Triple
T29422952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boxer |
E746202
|
entity |
| Predicate | missionVariant |
P171477
|
FINISHED |
| Object | armored personnel carrier variant |
—
|
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: armored personnel carrier variant | Statement: [Boxer, missionVariant, armored personnel carrier variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionVariant Context triple: [Boxer, missionVariant, armored personnel carrier variant]
-
A.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
B.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
-
C.
missionConfiguration
Indicates the specific setup, parameters, and conditions under which a mission is planned or executed.
-
D.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
E.
missionDesign
Indicates the relationship in which an entity plans, structures, and specifies the objectives, constraints, and procedures for carrying out a mission.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 28, 2026, 3:07 p.m.