Triple
T36545362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falls of Rauros |
E901126
|
entity |
| Predicate | marksSouthernEndOf |
P5249
|
FINISHED |
| Object | Nen Hithoel |
—
|
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: Nen Hithoel | Statement: [Falls of Rauros, marksSouthernEndOf, Nen Hithoel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksSouthernEndOf Context triple: [Falls of Rauros, marksSouthernEndOf, Nen Hithoel]
-
A.
marksBoundaryIn
Indicates that one entity serves as a boundary or delimiter within, or for a specific region or structure of, another entity.
-
B.
hasSouthernTerminus
chosen
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
-
C.
southernTerminusVariant
Indicates a variant or alternative form of the southern endpoint or terminus of something (such as a route, line, or boundary).
-
D.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
E.
marker
Indicates a relationship where one entity serves as a sign, label, or indicator that identifies, distinguishes, or signals a property or status of another entity.
- 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.