Triple
T36979613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Know, Teach, Replicate |
E914789
|
entity |
| Predicate | reflectsMissionTo |
P186845
|
FINISHED |
| Object | understand adversary space capabilities |
—
|
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: understand adversary space capabilities | Statement: [Know, Teach, Replicate, reflectsMissionTo, understand adversary space capabilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsMissionTo Context triple: [Know, Teach, Replicate, reflectsMissionTo, understand adversary space capabilities]
-
A.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
-
B.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
C.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
-
D.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
E.
tieneMisión
Indicates that an entity is assigned or carries out a specific mission or task.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.