Triple
T34715818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Littoria |
E1000768
|
entity |
| Predicate | foundingRegime |
P77515
|
FINISHED |
| Object | Italian Fascism |
—
|
NE NERFINISHED |
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: Italian Fascism | Statement: [Littoria, foundingRegime, Italian Fascism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingRegime Context triple: [Littoria, foundingRegime, Italian Fascism]
-
A.
historicalRegime
chosen
Indicates that one entity functioned as a governing regime or ruling authority over another entity during a specific historical period.
-
B.
politicalRegimeEstablished
Indicates that a particular political regime has been formally created and brought into effect in a given place or context.
-
C.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
-
D.
laterPoliticalSystemUnderRule
Indicates that one political system came under the rule or authority of another political system at a later point in time.
-
E.
constitutionalRegime
Indicates that one entity functions as the constitutional system or framework of governance under which another entity is organized or operates.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 3, 2026, 3:59 p.m.