Triple
T6472686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ground-based Midcourse Defense |
E145992
|
entity |
| Predicate | engagementEnvironment |
P70999
|
FINISHED |
| Object | space |
—
|
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 | Statement: [Ground-based Midcourse Defense, engagementEnvironment, space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementEnvironment Context triple: [Ground-based Midcourse Defense, engagementEnvironment, space]
-
A.
engagementArea
Indicates the spatial region or scope within which an entity’s actions, influence, or interactions are intended to occur.
-
B.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
C.
includesEngagement
Indicates that one entity incorporates or involves another entity in an engagement, interaction, or participatory activity.
-
D.
engagementCapability
Indicates the ability or capacity of one entity to initiate, conduct, or sustain an interaction or engagement with another entity.
-
E.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a3188488190a1b7452ede91ba5e |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067da970481908a038995ba7dfb4b |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:50 p.m.