Triple
T37315692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Osgiliath (War of the Ring) |
E926325
|
entity |
| Predicate | takesPlaceOnRiver |
P168595
|
FINISHED |
| Object | Anduin |
—
|
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: Anduin | Statement: [Battle of Osgiliath (War of the Ring), takesPlaceOnRiver, Anduin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesPlaceOnRiver Context triple: [Battle of Osgiliath (War of the Ring), takesPlaceOnRiver, Anduin]
-
A.
operatesOnRiver
Indicates that an entity conducts its operations or activities on, along, or directly involving a river.
-
B.
plannedOnRiver
Indicates that something is intended or designed to be located, constructed, or carried out on or along a river.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
riverineLocation
chosen
Indicates that something is located in, along, or directly associated with a river or river system.
-
E.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.