Triple
T36545380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falls of Rauros |
E901126
|
entity |
| Predicate | boatPassedOver |
P153011
|
FINISHED |
| Object | Boromir’s funeral boat |
—
|
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: Boromir’s funeral boat | Statement: [Falls of Rauros, boatPassedOver, Boromir’s funeral boat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatPassedOver Context triple: [Falls of Rauros, boatPassedOver, Boromir’s funeral boat]
-
A.
passesOverRiver
Indicates that one entity crosses above a river, typically via a bridge or similar structure, without entering the water.
-
B.
boatTraveledOn
chosen
Indicates that a boat moved or was transported along or across a specified body of water or route.
-
C.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
D.
crossesWaterBody
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
E.
acrossWaterFrom
Indicates that two entities are located on opposite sides of a body of water, separated by that water.
- 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_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.