Triple
T29578925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French legitimism |
E753519
|
entity |
| Predicate | hadPoliticalExpressionIn |
P132388
|
FINISHED |
| Object | Legitimist party |
—
|
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: Legitimist party | Statement: [French legitimism, hadPoliticalExpressionIn, Legitimist party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPoliticalExpressionIn Context triple: [French legitimism, hadPoliticalExpressionIn, Legitimist party]
-
A.
hasPoliticalActivityIn
Indicates that an entity engages in or is associated with political activities within a specified location or jurisdiction.
-
B.
hasPoliticalCurrent
chosen
Indicates that an entity is associated with, aligned to, or characterized by a particular political current, ideology, or movement.
-
C.
hasPoliticalComponent
Indicates that something includes, involves, or is influenced by political factors, interests, or considerations.
-
D.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
E.
hasPoliticalDialogue
Indicates that there is an exchange or interaction between entities involving political topics, issues, or negotiations.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7825c08190953242afe9572940 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:05 p.m.