Triple
T3335632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changing of the Guard |
E70133
|
entity |
| Predicate | guardUnitType |
P17521
|
FINISHED |
| Object | infantry |
—
|
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: infantry | Statement: [Changing of the Guard, guardUnitType, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardUnitType Context triple: [Changing of the Guard, guardUnitType, infantry]
-
A.
garrisonedUnit
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
-
B.
garrisonType
chosen
Indicates the specific kind or classification of military garrison associated with an entity.
-
C.
oversawUnitType
Indicates that an entity had supervisory or managerial responsibility over a particular type or category of unit.
-
D.
policeUnit
Indicates that one entity is a police unit (such as a department, squad, or division) associated with or responsible for another entity.
-
E.
controlUnitType
Indicates the specific kind or category of control unit associated with or assigned to an 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb197bd0481909a5cf7eab386e176 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.