Triple
T26802146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strathclyde valley |
E671129
|
entity |
| Predicate | historicKingdomCapital |
P190060
|
FINISHED |
| Object | Dumbarton |
—
|
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: Dumbarton | Statement: [Strathclyde valley, historicKingdomCapital, Dumbarton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicKingdomCapital Context triple: [Strathclyde valley, historicKingdomCapital, Dumbarton]
-
A.
eraOfHistoricalKingdom
Indicates the historical time period during which a particular kingdom existed or held prominence.
-
B.
associatedDynastyCapital
Indicates a relationship where a dynasty is linked to the city that served as its capital.
-
C.
foundedKingdom
Indicates that an entity established or created a kingdom as its founder.
-
D.
capitalCityDuringEra
Indicates that a particular city served as the capital of an entity (such as a country or region) during a specified historical era or time period.
-
E.
capitalOfHistoricalRule
chosen
Indicates that one place served as the capital city or seat of government for another entity during a specific historical period of its rule.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 27, 2026, 4:23 a.m.