Triple
T34640148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvenking's Halls |
E889532
|
entity |
| Predicate | usedForImprisonmentOf |
P22043
|
FINISHED |
| Object | Thorin Oakenshield |
—
|
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: Thorin Oakenshield | Statement: [Elvenking's Halls, usedForImprisonmentOf, Thorin Oakenshield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForImprisonmentOf Context triple: [Elvenking's Halls, usedForImprisonmentOf, Thorin Oakenshield]
-
A.
usedForImprisoning
chosen
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
-
B.
imprisonedFor
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
-
C.
sometimesImprisons
Indicates that one entity occasionally confines or incarcerates another entity, but not on a regular or constant basis.
-
D.
imprisonedWith
Indicates that two entities are confined or held in prison together at the same time and place.
-
E.
wasImprisonedIn
Indicates that an entity was held in confinement or incarcerated at a particular place or facility.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 2:04 a.m.