Triple
T33232876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger Center for Space Science Education |
E850744
|
entity |
| Predicate | hasOutcomeFocus |
P74555
|
FINISHED |
| Object | student engagement in STEM |
—
|
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: student engagement in STEM | Statement: [Challenger Center for Space Science Education, hasOutcomeFocus, student engagement in STEM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeFocus Context triple: [Challenger Center for Space Science Education, hasOutcomeFocus, student engagement in STEM]
-
A.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
B.
hasOutcomeDeterminedBy
Indicates that the result or consequence of one entity is decided, controlled, or directly influenced by another entity.
-
C.
outcomeFocus
chosen
Indicates that the primary emphasis or attention is placed on the results or consequences of an action or process.
-
D.
hasOutcomeClass
Indicates that something is associated with a particular category or type of outcome.
-
E.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:31 a.m.