Triple
T4292737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosario |
E99633
|
entity |
| Predicate | hasRiverFrontLength |
P1568
|
FINISHED |
| Object | approximately 15 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: approximately 15 km | Statement: [Rosario, hasRiverFrontLength, approximately 15 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverFrontLength Context triple: [Rosario, hasRiverFrontLength, approximately 15 km]
-
A.
hasWaterfrontArea
Indicates that an entity possesses or includes an area directly adjacent to or bordering a body of water.
-
B.
shorelineLength
chosen
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
C.
frontLength
Indicates the length measurement of the front side or edge of an object relative to its overall dimensions.
-
D.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
-
E.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35082228081908504e3fd7c4ca1e8 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.