Triple
T3307490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Reserve armoured units |
E69484
|
entity |
| Predicate | trainsWith |
P788
|
FINISHED |
| Object | regular army armoured units |
—
|
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: regular army armoured units | Statement: [Army Reserve armoured units, trainsWith, regular army armoured units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainsWith Context triple: [Army Reserve armoured units, trainsWith, regular army armoured units]
-
A.
trains
chosen
Indicates that one entity teaches, instructs, or coaches another entity to develop skills, knowledge, or abilities.
-
B.
trainsForOccupation
Indicates that an entity undergoes training or preparation aimed at qualifying for or performing a specific occupation.
-
C.
usesTrainNumber
Indicates that one entity operates, identifies, or references another entity by a specific train number.
-
D.
notableTrain
Indicates that there is a train or rail service associated with the subject that is considered notable or significant in some way.
-
E.
railwayCarriageUsedFor
Indicates that a railway carriage is employed or designated for a particular purpose, function, or type of use.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0cc15088190b51c311c6590df04 |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.