Triple
T17625005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timavo River |
E429816
|
entity |
| Predicate | undergroundLengthApproxKm |
P121757
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [Timavo River, undergroundLengthApproxKm, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergroundLengthApproxKm Context triple: [Timavo River, undergroundLengthApproxKm, 40]
-
A.
hasUndergroundLength
chosen
Indicates the extent of an object or structure that lies below ground level, measured as its underground length.
-
B.
undergroundTourAvailable
Indicates that guided tours taking place below ground level (such as in tunnels, caves, or basements) are offered at this location or for this attraction.
-
C.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
D.
undergroundCavernLength
Indicates the measured linear extent or distance from one end to the other of an underground cavern.
-
E.
operatedUnderground
Indicates that an entity conducted its activities or operations beneath the surface of the ground, rather than at or above ground level.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbb2a348190982658d495c81da0 |
completed | April 19, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.