Triple
T36550426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tunnels of Torech Ungol |
E901243
|
entity |
| Predicate | describedInVolume |
P519
|
FINISHED |
| Object | The Two Towers |
—
|
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 Two Towers | Statement: [tunnels of Torech Ungol, describedInVolume, The Two Towers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedInVolume Context triple: [tunnels of Torech Ungol, describedInVolume, The Two Towers]
-
A.
describedIn
chosen
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
describedAsIn
Indicates that one entity is described or characterized in a particular way within a specified information source or context.
-
C.
foundInVolume
Indicates that one entity is physically or logically contained within, or occurs in, a specific volume (such as a book volume, data volume, or bounded collection).
-
D.
describedAt
Indicates that something is explained, characterized, or detailed in a particular source, context, or location.
-
E.
documentedInBook
Indicates that information about an entity is recorded or described within a particular book.
- 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_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 4:11 p.m.