Triple
T29024441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barad-dûr |
E737548
|
entity |
| Predicate | strengthTiedTo |
P165932
|
FINISHED |
| Object | the One Ring |
—
|
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 One Ring | Statement: [Barad-dûr, strengthTiedTo, the One Ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthTiedTo Context triple: [Barad-dûr, strengthTiedTo, the One Ring]
-
A.
strengthType
Indicates the specific category or nature of strength associated with an entity or relationship (e.g., physical, structural, or conceptual strength).
-
B.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
-
C.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
D.
strongestIn
Indicates that one entity possesses the greatest strength or power within a specified group, context, or comparison set.
-
E.
tiedTo
Indicates that one entity is physically or figuratively fastened, bound, or otherwise constrained in connection to another entity.
- F. None of above. chosen
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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66007a5d8819085fcc6651a89a189 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 9:51 a.m.