Triple
T7080859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perpignan |
E164948
|
entity |
| Predicate | distanceToToulouseKm |
P45962
|
FINISHED |
| Object | about 200 |
—
|
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: about 200 | Statement: [Perpignan, distanceToToulouseKm, about 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToToulouseKm Context triple: [Perpignan, distanceToToulouseKm, about 200]
-
A.
distanceFromToulouse
chosen
Indicates the measured spatial distance between a given entity and the location of Toulouse.
-
B.
distanceFromFoixKilometres
Indicates the physical distance, measured in kilometers, between a given place or entity and the location of Foix.
-
C.
distanceFromLyon
Indicates the spatial distance between a given entity and the city of Lyon.
-
D.
distanceToFrance
Indicates the spatial distance between a given entity and the country of France.
-
E.
distanceToMetzKilometers
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Metz.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4f1f5748190b214856bcfc70d81 |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.