Triple
T10671072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kai (quay) |
E251485
|
entity |
| Predicate | typicallyLocatedAlong |
P2409
|
FINISHED |
| Object | river |
—
|
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: river | Statement: [Kai (quay), typicallyLocatedAlong, river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyLocatedAlong Context triple: [Kai (quay), typicallyLocatedAlong, river]
-
A.
locatedAlong
chosen
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
B.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
C.
extendsAlongCoastOf
Indicates that one entity stretches or runs parallel along the coastline of another entity.
-
D.
situatedOnTransportRoute
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
E.
partlyLocatedOn
Indicates that one entity is situated such that only a portion of it lies on or within the spatial extent 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f8648a248190a3bd284c569152e4 |
completed | April 9, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:09 p.m.