Triple
T13156098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSC LC-39A |
E312593
|
entity |
| Predicate | hasCrewAccessArm |
P79770
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [KSC LC-39A, hasCrewAccessArm, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewAccessArm Context triple: [KSC LC-39A, hasCrewAccessArm, yes]
-
A.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
B.
hasArms
Indicates that an entity possesses arms as physical appendages.
-
C.
armsControl
Indicates a relationship where parties engage in limiting, regulating, or reducing weapons and military capabilities, often through agreements or treaties.
-
D.
hasArmedWing
Indicates that an entity maintains, controls, or is associated with an organized armed or military wing.
-
E.
crewAccess
chosen
Indicates that one entity has permission or authorization to access or enter an area, resource, or function reserved for crew members.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.