Triple
T2859301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Limburg |
E63278
|
entity |
| Predicate | historicalGovernmentForm |
P17921
|
FINISHED |
| Object | feudal 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: feudal monarchy | Statement: [Duke of Limburg, historicalGovernmentForm, feudal monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalGovernmentForm Context triple: [Duke of Limburg, historicalGovernmentForm, feudal monarchy]
-
A.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
B.
governmentFormedBy
Indicates that a particular government is created, established, or brought into power by a specified entity or group.
-
C.
currentConstitutionalFormSince
Indicates the date or point in time from which the entity has had its present constitutional form or system of government.
-
D.
politicalSystemHistorical
Indicates a relationship where a political system is characterized or analyzed in terms of its historical development, context, or evolution.
-
E.
governmentFormDuringEra
chosen
Indicates the specific form or system of government that was in place during a particular historical era or time period.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf8aec3c8190a4168d8c916b5268 |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.