Triple
T10957655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of the Three Guarantees |
E258885
|
entity |
| Predicate | includedFormerFaction |
P1168
|
FINISHED |
| Object | royalist forces |
—
|
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: royalist forces | Statement: [Army of the Three Guarantees, includedFormerFaction, royalist forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedFormerFaction Context triple: [Army of the Three Guarantees, includedFormerFaction, royalist forces]
-
A.
formerAllyOf
Indicates that an entity was once an ally of another entity but that alliance has since ended.
-
B.
formerMemberOf
chosen
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
-
C.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
D.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
E.
hasFactionalOrigin
Indicates that something originates from, or is derived from, a particular faction or internal subgroup.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77126d9288190aa5daf2ba83d731d |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.