Triple
T37593518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halls of Reflection |
E935319
|
entity |
| Predicate | connectedInstance |
P37306
|
FINISHED |
| Object | The Forge of Souls |
—
|
NE NERFINISHED |
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: The Forge of Souls | Statement: [Halls of Reflection, connectedInstance, The Forge of Souls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedInstance Context triple: [Halls of Reflection, connectedInstance, The Forge of Souls]
-
A.
currentlyLinkedTo
Indicates that one entity is at this moment connected or associated with another entity in an ongoing relationship or linkage.
-
B.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
C.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
-
D.
connectedToEvent
Indicates that an entity has a direct association or linkage with a specific event.
-
E.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
- F. None of above.
Provenance (3 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_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:18 p.m.