Triple
T35647274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederado territory |
E1030044
|
entity |
| Predicate | inWorldGovernmentType |
P66248
|
FINISHED |
| Object | military regime |
—
|
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: military regime | Statement: [Confederado territory, inWorldGovernmentType, military regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inWorldGovernmentType Context triple: [Confederado territory, inWorldGovernmentType, military regime]
-
A.
governmentType
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
B.
hasGovernmentTypeCountry
chosen
Indicates that a country possesses or is characterized by a particular form or type of government.
-
C.
typeOfGovernmentInstitution
Indicates that one entity is a government institution of the type or category specified by the other entity.
-
D.
typeOfGovernmentForces
Indicates the specific kind or classification of government-controlled military or security forces involved in a situation or context.
-
E.
typeOfGovernmentAfter
Indicates the form of government that exists or is established in a place following a specified event 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.