Triple
T37837826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John I, Duke of Brittany |
E943384
|
entity |
| Predicate | allegianceShiftedBetween |
P128974
|
FINISHED |
| Object | King of France |
—
|
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: King of France | Statement: [John I, Duke of Brittany, allegianceShiftedBetween, King of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegianceShiftedBetween Context triple: [John I, Duke of Brittany, allegianceShiftedBetween, King of France]
-
A.
changeOfAllegiance
chosen
Indicates a shift in loyalty or support from one party, group, or cause to another.
-
B.
hadAllegiance
Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
-
C.
allianceShiftedFrom
Indicates that an entity changed its alliance from one party or group to another.
-
D.
hadAllegianceDuring
Indicates that an entity was formally loyal or committed to another entity for a specified period of time.
-
E.
refusedAllegianceTo
Indicates that one entity declined or rejected giving loyalty, support, or obedience to another entity.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:19 p.m.