Triple
T29263315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assault Amphibious Vehicle |
E741908
|
entity |
| Predicate | propulsionOnLand |
P24153
|
FINISHED |
| Object | tracked |
—
|
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: tracked | Statement: [Assault Amphibious Vehicle, propulsionOnLand, tracked]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propulsionOnLand Context triple: [Assault Amphibious Vehicle, propulsionOnLand, tracked]
-
A.
propulsionMedium
Indicates the medium or substance through which propulsion is generated or transmitted for movement.
-
B.
propulsionFeature
chosen
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
C.
propulsionTypeOfSystem
Indicates the type of propulsion mechanism that a system uses to generate thrust or movement.
-
D.
propulsionSource
Indicates the mechanism or system that provides thrust or driving force for an object’s movement.
-
E.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664dd47488190946f9a3f9c4a7d24 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:43 p.m.