Triple
T6255043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reggio Calabria |
E140141
|
entity |
| Predicate | distanceAcrossStraitToMessina |
P69746
|
FINISHED |
| Object | about 3 kilometers at narrowest point |
—
|
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 3 kilometers at narrowest point | Statement: [Reggio Calabria, distanceAcrossStraitToMessina, about 3 kilometers at narrowest point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceAcrossStraitToMessina Context triple: [Reggio Calabria, distanceAcrossStraitToMessina, about 3 kilometers at narrowest point]
-
A.
distanceToGenoa_km
Indicates the physical distance, measured in kilometers, between a given place or object and the city of Genoa.
-
B.
distanceFromMediterranean
Indicates the measured spatial distance between a given location and the Mediterranean Sea.
-
C.
distanceFromMestia
Indicates the spatial distance between a given place and the location of Mestia.
-
D.
distanceFromMiletus
Indicates the spatial distance between a given place or object and the location of Miletus.
-
E.
approxDistanceToMytilene
Indicates that one entity is located at an approximate distance from the place or reference point named Mytilene.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06363d6008190bf05e003b1f74497 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:24 p.m.