Triple
T17584804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Space Control Squadron |
E428293
|
entity |
| Predicate | capabilityArea |
P91017
|
FINISHED |
| Object | space superiority |
—
|
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: space superiority | Statement: [4th Space Control Squadron, capabilityArea, space superiority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capabilityArea Context triple: [4th Space Control Squadron, capabilityArea, space superiority]
-
A.
competenceArea
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
B.
includesCapabilityArea
chosen
Indicates that one entity encompasses or contains a specific capability area as part of its overall scope or functionality.
-
C.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
D.
assessmentAreaDefinedBy
Indicates that the scope or domain of an assessment is specified or delimited by a particular area or boundary.
-
E.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463d113b08190975506f3558c1eca |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.