Triple
T641238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty Years After |
E16742
|
entity |
| Predicate | hasProtagonistAllegiance |
P8706
|
FINISHED |
| Object | French monarchy |
—
|
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: French monarchy | Statement: [Twenty Years After, hasProtagonistAllegiance, French monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistAllegiance Context triple: [Twenty Years After, hasProtagonistAllegiance, French monarchy]
-
A.
hasProtagonist
chosen
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
allianceRole
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
-
C.
allianceStatus
Indicates the formal or informal cooperative relationship between entities, such as whether they are allies, neutral, or adversarial.
-
D.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
E.
hasPoliticalAlly
Indicates that one entity supports and cooperates with another in a political context, treating them as an ally in political activities or objectives.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f02bc2c8190b8a92b2505768c19 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.