Triple
T22176982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feuillant faction |
E548074
|
entity |
| Predicate | positionOnKing |
P147269
|
FINISHED |
| Object | sought to maintain Louis XVI on the throne with limited powers |
—
|
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: sought to maintain Louis XVI on the throne with limited powers | Statement: [Feuillant faction, positionOnKing, sought to maintain Louis XVI on the throne with limited powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnKing Context triple: [Feuillant faction, positionOnKing, sought to maintain Louis XVI on the throne with limited powers]
-
A.
opponentKing
Indicates that one entity is the king belonging to the opposing or rival side of the other entity.
-
B.
selectedAsKing
Indicates that an entity has been chosen or appointed to hold the position or role of king.
-
C.
hasKing
Indicates that an entity possesses or is ruled by a king.
-
D.
positionOnKuhn
Indicates the stance or viewpoint an entity holds regarding Kuhn’s theories or framework.
-
E.
servedKing
Indicates that one entity performed duties or services in allegiance or obedience to a king.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6d03488190b29872ff3f436237 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:34 p.m.