Triple
T34948103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garde du Directoire |
E1007908
|
entity |
| Predicate | governmentTypeProtected |
P220
|
FINISHED |
| Object | Directory |
—
|
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: Directory | Statement: [Garde du Directoire, governmentTypeProtected, Directory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentTypeProtected Context triple: [Garde du Directoire, governmentTypeProtected, Directory]
-
A.
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.
-
B.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
C.
governmentTypeAffected
Indicates that an action, event, or condition has an impact on the form, structure, or functioning of a government type.
-
D.
governmentTypeSupported
Indicates that an entity endorses, backs, or is in favor of a particular form or system of government.
-
E.
governmentTypeAttempted
Indicates that an entity has tried or aimed to establish, implement, or transition to a particular form of government.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a018c6b7178819097d5450a1e3c2408 |
completed | May 11, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_6a018a4f741c8190babe721a908e2f5e |
completed | May 11, 2026, 7:50 a.m. |
Created at: May 3, 2026, 4 p.m.