Triple
T11512186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Florence |
E272939
|
entity |
| Predicate | hadCapitalType |
P16430
|
FINISHED |
| Object | provincial capital |
—
|
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: provincial capital | Statement: [Province of Florence, hadCapitalType, provincial capital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCapitalType Context triple: [Province of Florence, hadCapitalType, provincial capital]
-
A.
hasCapitalType
chosen
Indicates that a specified location’s capital is of a particular type (e.g., political, administrative, or economic capital).
-
B.
hasCoCapital
Indicates that two or more cities share the status and functions of being capital cities of the same political or administrative entity.
-
C.
hasAssociatedCapital
Indicates that an entity is linked to a specific capital city that serves as its primary administrative or political center.
-
D.
sourceOfCapital
Indicates the origin or provider from which an entity obtains its financial capital or funding.
-
E.
hasCapitalFeature
Indicates that one entity possesses or is characterized by a primary or most important feature 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db7af688190b68668eb39d382a8 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.