Triple
T25765538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nosy Iranja |
E648872
|
entity |
| Predicate | distanceFromNosyBe |
P189702
|
FINISHED |
| Object | approximately 27 nautical miles |
—
|
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 27 nautical miles | Statement: [Nosy Iranja, distanceFromNosyBe, approximately 27 nautical miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromNosyBe Context triple: [Nosy Iranja, distanceFromNosyBe, approximately 27 nautical miles]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
distanceToSneek
Indicates the spatial distance between an entity and the location named Sneek.
-
C.
distanceFromBol
Indicates the measured distance between an entity and a specified beginning-of-line (BOL) reference point.
-
D.
distanceFromHo
Indicates the spatial distance measured from a specified reference point or origin labeled "Ho" to another entity.
-
E.
approxDistanceToJos
Indicates that one entity is located at an approximate distance from the entity referred to as Jos.
- F. None of above. chosen
Provenance (4 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: April 22, 2026, 5:10 a.m.