Triple
T37593477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halls of Stone |
E935318
|
entity |
| Predicate | associatedWithLore |
P102058
|
FINISHED |
| Object | Titans |
E18777
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Titans | Statement: [Halls of Stone, associatedWithLore, Titans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLore Context triple: [Halls of Stone, associatedWithLore, Titans]
-
A.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
B.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
-
C.
associatedLoch
Indicates that one entity is linked or connected to a particular loch (lake or sea inlet), typically by location, relevance, or contextual relationship.
-
D.
associatedWithLegacyOfBearer
Indicates that an entity is connected to, influenced by, or derived from the historical legacy or enduring impact of a specified bearer.
-
E.
associatedTale
chosen
Indicates that one entity is linked or connected to a particular tale, story, or narrative.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afdd627c81909e31b81b435a03cd |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.