Triple
T25152384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cellamare |
E630111
|
entity |
| Predicate | countryCapitalOfRegionDistanceRelation |
P33891
|
FINISHED |
| Object | near Bari |
—
|
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: near Bari | Statement: [Cellamare, countryCapitalOfRegionDistanceRelation, near Bari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCapitalOfRegionDistanceRelation Context triple: [Cellamare, countryCapitalOfRegionDistanceRelation, near Bari]
-
A.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
-
C.
countryCapitalNearby
chosen
Indicates that a country’s capital city is geographically close to a specified location or entity.
-
D.
prefecturalCapitalDistanceRelation
Indicates a spatial relationship specifying the distance between an entity and the capital city of its prefecture.
-
E.
countryCapitalRelation
Indicates that one entity is the capital city of the country represented by the other entity.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 6:30 a.m.