Triple
T2678285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deportivo de La Coruña |
E56511
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | A Coruña |
E198582
|
NE 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: A Coruña | Statement: [Deportivo de La Coruña, city, A Coruña]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A Coruña Context triple: [Deportivo de La Coruña, city, A Coruña]
-
A.
A Coruña
chosen
A Coruña is a coastal city in northwestern Spain known for its historic lighthouse, the Tower of Hercules, and its role as an important cultural and economic center in the region.
-
B.
Pontevedra
Pontevedra is a coastal municipality in the province of Capiz in the Philippines, known for its fishing communities and agricultural economy.
-
C.
Pontevedra
Pontevedra is a coastal province in northwestern Spain known for its historic towns, Atlantic landscapes, and location within the autonomous community of Galicia.
-
D.
Ferrol
Ferrol is a coastal city and major naval shipbuilding center in the Galicia region of northwestern Spain.
-
E.
Vigo
Vigo is a major industrial and port city in northwestern Spain, known for its shipbuilding, fishing industry, and location on the Atlantic coast of Galicia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b697fc8190a5ec8b75ee2ad238 |
completed | March 7, 2026, 7:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afb679d5bc8190b2dd4edeaf09b1e7 |
completed | March 10, 2026, 6:13 a.m. |
Created at: March 6, 2026, 9:54 p.m.