Triple
T5394995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arendal Line |
E120629
|
entity |
| Predicate | geographicFeatureTypeCrossed |
P225
|
FINISHED |
| Object | rivers |
—
|
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: rivers | Statement: [Arendal Line, geographicFeatureTypeCrossed, rivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicFeatureTypeCrossed Context triple: [Arendal Line, geographicFeatureTypeCrossed, rivers]
-
A.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
B.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
C.
crossesMountainRangeTo
Indicates that one entity traverses from one side of a mountain range to the other, passing across or through it as a route or connection.
-
D.
continentCrossed
Indicates that an entity has traversed from one side of a continent to the other, crossing the continent’s landmass.
-
E.
crossedByRiver
chosen
Indicates that a river passes across or through a specified area, feature, or route.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87441a208190b79561614759894b |
completed | March 20, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.