Triple
T30599668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celduin |
E778871
|
entity |
| Predicate | flowsSouthOf |
P85489
|
FINISHED |
| Object | Erebor |
—
|
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: Erebor | Statement: [Celduin, flowsSouthOf, Erebor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsSouthOf Context triple: [Celduin, flowsSouthOf, Erebor]
-
A.
flowsSouthTo
chosen
Indicates that something moves or is directed in a generally southward direction until it reaches or connects with another location or entity.
-
B.
flowsSouthwardTo
Indicates that something moves or is directed in a generally southward direction until it reaches or connects with another location or entity.
-
C.
flowsNorthOf
Indicates that one entity (typically a watercourse or current) moves in a generally northward direction while remaining geographically north of the other entity.
-
D.
flowsNorthFrom
Indicates that something moves or travels in a generally northward direction starting from a specified origin.
-
E.
flowsNorthward
Indicates that the subject moves or travels in a generally northward direction relative to a reference frame or location.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:25 p.m.