Triple
T37523728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES-A |
E932849
|
entity |
| Predicate | capitalOfRepresentedSubdivision |
P50006
|
FINISHED |
| Object | Alicante city |
—
|
NE NERFINISHED |
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: Alicante city | Statement: [ES-A, capitalOfRepresentedSubdivision, Alicante city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfRepresentedSubdivision Context triple: [ES-A, capitalOfRepresentedSubdivision, Alicante city]
-
A.
capitalOfSubdivision
chosen
Indicates that a place serves as the administrative capital of a specified subnational division (such as a state, province, or region).
-
B.
municipalityCapital
Indicates that one entity serves as the administrative capital or seat of government for a given municipality.
-
C.
capitalCitySubdivisionOf
Indicates that a capital city is an administrative or territorial subdivision of a larger governing region or entity.
-
D.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
E.
capitalOfReferencedRegion
Indicates that one entity serves as the capital city or administrative center of the region referenced by another 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:17 p.m.