Triple
T21502835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebersdorf |
E530521
|
entity |
| Predicate | governmentTypeAsCapital |
P144639
|
FINISHED |
| Object | monarchy |
—
|
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: monarchy | Statement: [Ebersdorf, governmentTypeAsCapital, monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentTypeAsCapital Context triple: [Ebersdorf, governmentTypeAsCapital, monarchy]
-
A.
governmentType
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
B.
governmentTypeStrengthened
Indicates that the form or structure of a government has been reinforced, consolidated, or made more powerful or stable relative to its previous state.
-
C.
governmentTypeSupported
Indicates that an entity endorses, backs, or is in favor of a particular form or system of government.
-
D.
typeOfGovernmentAfter
Indicates the form of government that exists or is established in a place following a specified event or time period.
-
E.
typeOfPolity
Indicates that one entity is a political unit and the other specifies the kind or classification of that polity (e.g., empire, kingdom, republic).
- F. None of above. chosen
Provenance (4 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea5deb388190a89a1f94285b7e55 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:24 p.m.