Triple
T33783209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio (León) |
E865715
|
entity |
| Predicate | militaryUnitTypePresent |
P81775
|
FINISHED |
| Object | legionaries |
—
|
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: legionaries | Statement: [Legio (León), militaryUnitTypePresent, legionaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryUnitTypePresent Context triple: [Legio (León), militaryUnitTypePresent, legionaries]
-
A.
isAboutMilitaryUnit
Indicates that something (such as a document, statement, or resource) concerns, discusses, or pertains to a specific military unit.
-
B.
hasMilitaryType
chosen
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
C.
militaryUnitOf
Indicates that one entity is a military unit that belongs to, is part of, or is under the command or organizational structure of another entity.
-
D.
usesMilitaryUnit
Indicates that one entity employs, deploys, or otherwise makes operational use of a specific military unit.
-
E.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:45 a.m.