Triple
T32526727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NC-212 |
E831334
|
entity |
| Predicate | missionAdaptability |
P23258
|
FINISHED |
| Object | multi-role |
—
|
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: multi-role | Statement: [NC-212, missionAdaptability, multi-role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionAdaptability Context triple: [NC-212, missionAdaptability, multi-role]
-
A.
aimsToAdapt
Indicates that one entity intends to modify or adjust itself, another entity, or a situation in order to better fit certain conditions, requirements, or environments.
-
B.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
-
C.
missionStrategy
Indicates the overarching plan, approach, or method an entity adopts to achieve a specific mission or objective.
-
D.
missionVariant
Indicates a specific version or configuration of a mission that differs from the standard or base mission.
-
E.
missionCharacteristic
chosen
Indicates that a mission possesses a specific attribute, feature, or quality that characterizes its nature or execution.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:01 a.m.