Triple
T34120045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paiva River |
E875096
|
entity |
| Predicate | PaivaWalkwaysLength |
P178420
|
FINISHED |
| Object | about 8.7 km |
—
|
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: about 8.7 km | Statement: [Paiva River, PaivaWalkwaysLength, about 8.7 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PaivaWalkwaysLength Context triple: [Paiva River, PaivaWalkwaysLength, about 8.7 km]
-
A.
walkwayType
Indicates the specific kind or classification of a walkway associated with an entity (e.g., sidewalk, footpath, boardwalk).
-
B.
footpathWidth
Indicates the measured or designated width of a footpath in the context of a spatial or infrastructural relationship.
-
C.
hasAirportWalkway
Indicates that there is a pedestrian walkway connection associated with or leading to an airport.
-
D.
walksRoute
Indicates that an entity follows or travels along a specific route by walking.
-
E.
walks
Indicates that an entity moves on foot from one place to another, typically at a regular, moderate pace.
- F. None of above. chosen
Provenance (4 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:53 a.m.