Triple
T35527559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Advocate |
E1026711
|
entity |
| Predicate | alignedWithStable |
P6442
|
FINISHED |
| Object | The Bloodline |
—
|
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: The Bloodline | Statement: [The Advocate, alignedWithStable, The Bloodline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignedWithStable Context triple: [The Advocate, alignedWithStable, The Bloodline]
-
A.
alignsWith
chosen
Indicates that one entity is in agreement, harmony, or consistent correspondence with another in terms of position, direction, standard, or principle.
-
B.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
C.
laterAlignedWith
Indicates that one entity becomes aligned with or matches another entity at a later point in time, rather than initially.
-
D.
originallyAlignedWith
Indicates that an entity was initially in agreement, support, or association with another entity or group, regardless of any later changes in stance or affiliation.
-
E.
isAlignedBy
Indicates that one entity is positioned, oriented, or arranged in accordance with another entity or a specified reference.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.