Triple
T30014976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boxer RCH 155 |
E762569
|
entity |
| Predicate | turretControl |
P168356
|
FINISHED |
| Object | remote from hull |
—
|
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: remote from hull | Statement: [Boxer RCH 155, turretControl, remote from hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turretControl Context triple: [Boxer RCH 155, turretControl, remote from hull]
-
A.
turret
Indicates that an entity is equipped with or associated with a turret, typically a rotating weapon or defense mechanism.
-
B.
turretPlacement
Indicates the spatial or positional relationship defining where a turret is placed relative to its environment or reference objects.
-
C.
turretDesign
Indicates a relationship where one entity specifies or defines the design or configuration of a turret associated with another entity.
-
D.
turretBasedOn
Indicates that one turret is derived from, modeled after, or constructed using the design or components of another turret.
-
E.
turretCount
Indicates the number of turrets associated with or mounted on a given 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679838da08190a06048a2b5f60f70 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:45 p.m.