Triple
T37027061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgar auxiliaries |
E916382
|
entity |
| Predicate | likelyUnitType |
P28425
|
FINISHED |
| Object | cavalry |
—
|
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: cavalry | Statement: [Bulgar auxiliaries, likelyUnitType, cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyUnitType Context triple: [Bulgar auxiliaries, likelyUnitType, cavalry]
-
A.
associatedUnitType
chosen
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
B.
mayIncludeUnitType
Indicates that something is allowed to contain or be associated with a particular type of unit.
-
C.
mayHaveUnit
Indicates that an entity can optionally be associated with a specific unit of measurement.
-
D.
listedUnit
Indicates that an entity is specified or recorded as a particular unit in a list or catalog.
-
E.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.