Triple
T20855539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samaritan armoured ambulance |
E513468
|
entity |
| Predicate | mayMount |
P57768
|
FINISHED |
| Object | 7.62 mm machine gun for self-defence |
—
|
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: 7.62 mm machine gun for self-defence | Statement: [Samaritan armoured ambulance, mayMount, 7.62 mm machine gun for self-defence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayMount Context triple: [Samaritan armoured ambulance, mayMount, 7.62 mm machine gun for self-defence]
-
A.
mountOf
Indicates that one entity serves as the mount or riding animal/creature used by another entity.
-
B.
mountingInterface
chosen
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
-
C.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
D.
guardMounting
Indicates the action of assigning or taking up a position for guard duty, typically as part of a scheduled security or watch rotation.
-
E.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a81ac4819084a07625b8ed4ec5 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.