Triple
T8053405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiumelatte |
E187730
|
entity |
| Predicate | riverLengthCharacteristic |
P25274
|
FINISHED |
| Object | very short |
—
|
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: very short | Statement: [Fiumelatte, riverLengthCharacteristic, very short]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverLengthCharacteristic Context triple: [Fiumelatte, riverLengthCharacteristic, very short]
-
A.
waterwayLengthKilometres
Indicates the total length of a waterway, measured in kilometres.
-
B.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
C.
riverKilometerContext
Indicates the position or context of something along a river, measured in river kilometers from a defined reference point.
-
D.
hydrologicalCharacteristic
chosen
Indicates a relationship where a hydrological feature or condition (such as water flow, level, or behavior) characterizes or describes another entity.
-
E.
hasLongestRiver
Indicates that one entity possesses or contains the river that is longer than any other river associated with the compared entities.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7c425c8190aa1b2f534afeb58c |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.