Triple
T6073418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel of Bulgaria |
E135339
|
entity |
| Predicate | vassalOrAlly |
P7255
|
FINISHED |
| Object | various local Slavic and Vlach leaders |
—
|
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: various local Slavic and Vlach leaders | Statement: [Samuel of Bulgaria, vassalOrAlly, various local Slavic and Vlach leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vassalOrAlly Context triple: [Samuel of Bulgaria, vassalOrAlly, various local Slavic and Vlach leaders]
-
A.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
B.
historicallyAlliedWith
Indicates that two entities have been political, military, or strategic allies during some period in the past.
-
C.
laterAlliesWith
Indicates that two entities become allies at a later time, after not being allied initially.
-
D.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
E.
vassalsOf
chosen
Indicates that one entity serves as a subordinate or dependent vassal under the authority or suzerainty of 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0575b9bc08190a78b3082b9ccf00c |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.