Triple
T33964802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-14 Armata |
E870821
|
entity |
| Predicate | hasCrewPlacement |
P175338
|
FINISHED |
| Object | armored crew capsule in 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: armored crew capsule in hull | Statement: [T-14 Armata, hasCrewPlacement, armored crew capsule in hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewPlacement Context triple: [T-14 Armata, hasCrewPlacement, armored crew capsule in hull]
-
A.
hasCrewFeature
Indicates that a crew possesses or is characterized by a particular feature, attribute, or capability.
-
B.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
C.
hasCrewMember
Indicates that an entity includes or employs another entity as a member of its crew.
-
D.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
E.
hasCrewedComponent
chosen
Indicates that an entity includes or is associated with a component that is operated or occupied by a crew.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 1:50 a.m.