Triple
T17972147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Champagne |
E449371
|
entity |
| Predicate | unionWithFrenchCrownDate |
P11440
|
FINISHED |
| Object | 1284 |
—
|
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: 1284 | Statement: [County of Champagne, unionWithFrenchCrownDate, 1284]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionWithFrenchCrownDate Context triple: [County of Champagne, unionWithFrenchCrownDate, 1284]
-
A.
integratedIntoFrenchCrown
Indicates that a territory, institution, or authority was formally absorbed into and brought under the direct control of the French royal state.
-
B.
dateOfUnionFormation
Indicates the date on which a union was formally established or came into existence.
-
C.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
D.
dynasticUnion
Indicates a political relationship in which two or more distinct states are ruled by the same dynasty or monarch while formally remaining separate entities.
-
E.
crownUnionWith
chosen
Indicates the formal unification of two or more political entities under a single crown or sovereign authority.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fb58c481909726d6f916f6f646 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.