Triple
T36548324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isildur’s Bane |
E901191
|
entity |
| Predicate | laterFoundBy |
P70361
|
FINISHED |
| Object | Déagol |
—
|
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: Déagol | Statement: [Isildur’s Bane, laterFoundBy, Déagol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterFoundBy Context triple: [Isildur’s Bane, laterFoundBy, Déagol]
-
A.
wasUncoveredBy
Indicates that something previously hidden, unknown, or concealed became revealed or discovered through the actions or efforts of a particular agent or process.
-
B.
laterDiscovered
Indicates that one entity was discovered or found at a time subsequent to the discovery of another entity.
-
C.
foundAfter
chosen
Indicates that one entity is discovered or located at a point in time later than another specified entity.
-
D.
foundAs
Indicates that one entity is discovered, identified, or observed in the role, form, or state represented by another entity.
-
E.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00ada2903481908b28ce55ef97a6c2 |
completed | May 10, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_6a00ad5d23788190b3f9e2de761d39bb |
completed | May 10, 2026, 4:07 p.m. |
Created at: May 3, 2026, 4:11 p.m.