Triple
T33111907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ring of Barahir |
E847351
|
entity |
| Predicate | identifiesBearerAs |
P65465
|
FINISHED |
| Object | Heir of Isildur |
—
|
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: Heir of Isildur | Statement: [Ring of Barahir, identifiesBearerAs, Heir of Isildur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesBearerAs Context triple: [Ring of Barahir, identifiesBearerAs, Heir of Isildur]
-
A.
eraOfBearer
Indicates that a time period or era is associated with, or characterizes, the bearer entity.
-
B.
notableBearerDescription
chosen
Indicates that the subject has a notable bearer, with the object providing a textual description of that bearer’s significance or identity.
-
C.
bearerByname
Indicates that an entity is known or referred to by a particular byname or secondary name.
-
D.
bearerInstanceOf
Indicates that a bearer (such as an agent, object, or entity) is an instance or specific realization of a more general class, type, or role.
-
E.
relationViaBearer
Indicates that one entity is related to another indirectly through an intermediate bearer or carrier that holds or mediates the relationship between them.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.