Triple
T21130270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC-41 |
E520665
|
entity |
| Predicate | supportsLaunchOperations |
P13868
|
FINISHED |
| Object | countdown and control facilities |
—
|
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: countdown and control facilities | Statement: [SLC-41, supportsLaunchOperations, countdown and control facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLaunchOperations Context triple: [SLC-41, supportsLaunchOperations, countdown and control facilities]
-
A.
supportsOperationsIn
chosen
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
B.
launchesSupported
Indicates that one entity is capable of initiating or starting another entity or process.
-
C.
supportsOperationsWith
Indicates that one entity enables, facilitates, or is compatible with the execution of operations involving another entity.
-
D.
operationSupported
Indicates that a particular operation is available and can be performed or handled by a given entity or system.
-
E.
hasLaunch
Indicates that an entity initiates or carries out the launch of another entity (such as a product, mission, or event).
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723556ec08190a2ade96c76f9cec7 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.