Triple
T17759464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Württemberg-Hohenzollern |
E443330
|
entity |
| Predicate | establishedAsStateOfFederalRepublic |
P13884
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [Württemberg-Hohenzollern, establishedAsStateOfFederalRepublic, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsStateOfFederalRepublic Context triple: [Württemberg-Hohenzollern, establishedAsStateOfFederalRepublic, 1949]
-
A.
succeededToStatehoodAs
Indicates that one entity became a sovereign state as the direct successor to another entity’s prior political or territorial status.
-
B.
joinedFederalRepublic
chosen
Indicates that an entity became a member of, or was incorporated into, a federal republic.
-
C.
becameRepublicOn
Indicates the date or point in time when an entity transitioned to a republican form of government.
-
D.
statehoodYear
Indicates the year in which an entity officially became a recognized state or attained statehood status.
-
E.
statehoodEvent
Indicates an event or process through which an entity attains, changes, or loses the status of being a recognized state.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48420ad188190aeb0f4ec1d23ee5c |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.