Triple
T13291934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trephina Gorge |
E316578
|
entity |
| Predicate | distanceFromInKilometres |
P22795
|
FINISHED |
| Object | approximately 85 |
—
|
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 85 | Statement: [Trephina Gorge, distanceFromInKilometres, approximately 85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromInKilometres Context triple: [Trephina Gorge, distanceFromInKilometres, approximately 85]
-
A.
approximateDistanceKm
chosen
Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
-
B.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
C.
distanceProvidedBy
Indicates that a specific distance value is supplied or made available by a particular source or provider.
-
D.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
E.
distance
Indicates the spatial separation or length between two points, objects, or locations.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.