Triple
T3474600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Parma |
E73340
|
entity |
| Predicate | hasHistoricalGovernmentForm |
P49184
|
FINISHED |
| Object | duchy |
—
|
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: duchy | Statement: [Prince of Parma, hasHistoricalGovernmentForm, duchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalGovernmentForm Context triple: [Prince of Parma, hasHistoricalGovernmentForm, duchy]
-
A.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
B.
hasLocalGovernmentHistory
Indicates that an entity has a documented history or record of its local governmental structure, activities, or developments.
-
C.
politicalSystemHistorical
Indicates a relationship where a political system is characterized or analyzed in terms of its historical development, context, or evolution.
-
D.
governmentFormedBy
Indicates that a particular government is created, established, or brought into power by a specified entity or group.
-
E.
historicalFormation
Indicates the process or circumstances through which something came into existence or took shape over time in history.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb580d4c819080bcc0bccd1e18e2 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:17 p.m.