Triple
T6954101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECV-197 |
E161196
|
entity |
| Predicate | secondaryMissionType |
P62593
|
FINISHED |
| Object | defense |
—
|
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: defense | Statement: [ECV-197, secondaryMissionType, defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryMissionType Context triple: [ECV-197, secondaryMissionType, defense]
-
A.
secondaryMissionField
chosen
Indicates a secondary or supporting operational area or objective associated with the primary mission.
-
B.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
C.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
D.
secondaryTarget
Indicates that an entity serves as an additional or subordinate target in relation to a primary target within a given context or action.
-
E.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.