Triple
T8489366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oto Melara 105 mm L/52 gun |
E200927
|
entity |
| Predicate | mountingPlatform |
P29518
|
FINISHED |
| Object | tanks |
—
|
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: tanks | Statement: [Oto Melara 105 mm L/52 gun, mountingPlatform, tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountingPlatform Context triple: [Oto Melara 105 mm L/52 gun, mountingPlatform, tanks]
-
A.
onboardPlatform
Indicates that an entity is being added, integrated, or enrolled onto a particular platform so it can start operating or participating there.
-
B.
mountingLocation
chosen
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
C.
boosterLandingPlatform
Indicates the platform or structure on which a rocket booster lands or is intended to land after its flight.
-
D.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
E.
ceremonialPlatform
Indicates a relationship where an entity serves as or is associated with a specially constructed platform used for ceremonies or ritual events.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5581d308190b47d76dd49a36529 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.