Triple
T1347074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haarlem |
E28594
|
entity |
| Predicate | hasProvinceCapitalStatusSince |
P334
|
FINISHED |
| Object | 1840s |
—
|
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: 1840s | Statement: [Haarlem, hasProvinceCapitalStatusSince, 1840s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProvinceCapitalStatusSince Context triple: [Haarlem, hasProvinceCapitalStatusSince, 1840s]
-
A.
isProvincialCapital
Indicates that a location serves as the administrative capital of a province within a country or region.
-
B.
stateCapitalSince
chosen
Indicates that one location has served as the official capital of a state continuously from a specified starting time.
-
C.
wasDeFactoCapitalOf
Indicates that a place functioned in practice as the capital of a political entity, even if it was not officially designated as such.
-
D.
servedAsNationalCapitalFrom
Indicates that a place functioned as the national capital of a country or political entity during a specified time period.
-
E.
hasCapitalDistrictStatus
Indicates that an administrative region holds the official status of being a capital district within a country or larger jurisdiction.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2406c488190b2c04d54d9c5e94c |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.