Triple
T29365487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine Varangian Guard |
E744703
|
entity |
| Predicate | receivedFromAllies |
P172153
|
FINISHED |
| Object | contingent of Rus warriors |
—
|
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: contingent of Rus warriors | Statement: [Byzantine Varangian Guard, receivedFromAllies, contingent of Rus warriors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedFromAllies Context triple: [Byzantine Varangian Guard, receivedFromAllies, contingent of Rus warriors]
-
A.
alliesIncluded
Indicates that the specified set or group explicitly includes one or more allied entities as members.
-
B.
alliedRecognition
Indicates that one entity formally acknowledges another as an ally or partner in a cooperative relationship.
-
C.
alliesOf
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
-
D.
alliedAgainstBy
Indicates that the subject is opposed by an entity that has formed an alliance with others against it.
-
E.
laterAlliesWith
Indicates that two entities become allies at a later time, after not being allied initially.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 28, 2026, 2:22 p.m.