Triple
T15887770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Am Mìle Rìoghail |
E385233
|
entity |
| Predicate | hasApproximateLengthInMeters |
P25800
|
FINISHED |
| Object | approximately 1800 |
—
|
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 1800 | Statement: [Am Mìle Rìoghail, hasApproximateLengthInMeters, approximately 1800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateLengthInMeters Context triple: [Am Mìle Rìoghail, hasApproximateLengthInMeters, approximately 1800]
-
A.
approximateLengthInMeters
chosen
Indicates the estimated or roughly measured length of something expressed in meters.
-
B.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
-
C.
hasApproximateDistanceScale
Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
-
D.
hasTunnelLengthApprox
Indicates that an entity has a tunnel whose length is approximately a specified value.
-
E.
navigableLengthApproxKm
Indicates the approximate distance, measured in kilometers, over which something (typically a waterway) can be navigated.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.