Triple
T32019155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabran (historical city) |
E817629
|
entity |
| Predicate | modernCountryCapitalDistanceRelation |
P10889
|
FINISHED |
| Object | north of Baku |
—
|
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: north of Baku | Statement: [Shabran (historical city), modernCountryCapitalDistanceRelation, north of Baku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCountryCapitalDistanceRelation Context triple: [Shabran (historical city), modernCountryCapitalDistanceRelation, north of Baku]
-
A.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
-
B.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
C.
departmentCapitalDistanceKm
Indicates the distance in kilometers between a department and its capital.
-
D.
modernCountryOfCapital
Indicates that a given city serves as the capital of a specified modern-day country.
-
E.
hasCountryCapitalConnection
Indicates a relationship in which a specific country is associated with its official capital city.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 12:16 a.m.