Triple
T34127224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Bar |
E875318
|
entity |
| Predicate | laterVassalTo |
P80032
|
FINISHED |
| Object | Kingdom of France |
—
|
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: Kingdom of France | Statement: [House of Bar, laterVassalTo, Kingdom of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterVassalTo Context triple: [House of Bar, laterVassalTo, Kingdom of France]
-
A.
vassalageOver
chosen
Indicates a hierarchical feudal relationship in which one party is a vassal subordinate to and owing allegiance or obligations to another.
-
B.
vassalageStart
Indicates the point in time when a vassalage relationship—where one party becomes subordinate or owes allegiance to another—officially begins.
-
C.
crownVassalTo
Indicates that a ruling authority formally grants vassal status to another party, establishing a hierarchical feudal relationship of allegiance and obligation.
-
D.
laterUsurpedBy
Indicates that one entity, after some time has passed, is overthrown or replaced in power, position, or authority by another entity.
-
E.
vassalageEndTime
Indicates the point in time at which a vassalage relationship between two entities formally ends.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:53 a.m.