Triple
T7625945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Own Oxfordshire Hussars |
E172630
|
entity |
| Predicate | laterEquipment |
P78180
|
FINISHED |
| Object | motor vehicles |
—
|
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: motor vehicles | Statement: [Queen's Own Oxfordshire Hussars, laterEquipment, motor vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEquipment Context triple: [Queen's Own Oxfordshire Hussars, laterEquipment, motor vehicles]
-
A.
laterEquipmentType
Indicates that one equipment type occurs or is used at a later time relative to another equipment type.
-
B.
laterProductType
Indicates that one product type occurs or is introduced after another product type in time or sequence.
-
C.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
D.
laterArm
Indicates that one event, state, or action occurs at a later time than another within the same arm or branch of a process or study.
-
E.
primaryEquipment
Indicates that one entity serves as the main or most important piece of equipment used by another entity.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6fe7323b0819081664662d2f26937 |
completed | March 27, 2026, 10:02 p.m. |
Created at: March 27, 2026, 3:56 p.m.