Triple
T25508966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosola |
E639318
|
entity |
| Predicate | alignmentWithDuchess |
P158614
|
FINISHED |
| Object | initially hostile |
—
|
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: initially hostile | Statement: [Bosola, alignmentWithDuchess, initially hostile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentWithDuchess Context triple: [Bosola, alignmentWithDuchess, initially hostile]
-
A.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
B.
createdDuchess
Indicates that an entity brought a duchess into existence, typically by giving birth to or otherwise originating her.
-
C.
alignmentLeader
Indicates that one entity serves as the primary leader or guiding figure responsible for directing or coordinating the alignment of others.
-
D.
alignmentShape
Indicates that one entity’s shape is arranged, oriented, or matched in position relative to another entity’s shape.
-
E.
alignmentWithMac
Indicates that something is compatible or properly configured to work with a Mac operating system or environment.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80844488190bbbaa6bd2e487940 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:48 p.m.