Triple
T25781118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Journey |
E649290
|
entity |
| Predicate | pathConcept |
P92560
|
FINISHED |
| Object | from headwaters to ocean |
—
|
LITERAL FINISHED |
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: from headwaters to ocean | Statement: [River Journey, pathConcept, from headwaters to ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pathConcept Context triple: [River Journey, pathConcept, from headwaters to ocean]
-
A.
pathTo
Indicates that one entity serves as a route, way, or means of reaching, accessing, or moving to another entity.
-
B.
pathRepresents
Indicates that a given path symbolically stands for, encodes, or denotes another entity, concept, or structure.
-
C.
pathFunction
Indicates a functional relationship that maps each point or state along a path to a corresponding value, position, or transformation defined by that path.
-
D.
addressesConcept
Indicates that one entity deals with, discusses, or responds to the subject matter represented by another entity.
-
E.
hasConceptualLocation
chosen
Indicates that something is associated with or situated within a particular abstract, conceptual, or non-physical context or domain.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fe6072588190a6a6703251ec02bf |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:38 a.m.