Triple
T15577494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle Enterprise |
E374405
|
entity |
| Predicate | postTestUse |
P23056
|
FINISHED |
| Object | fit checks at Kennedy Space Center |
—
|
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: fit checks at Kennedy Space Center | Statement: [Space Shuttle Enterprise, postTestUse, fit checks at Kennedy Space Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postTestUse Context triple: [Space Shuttle Enterprise, postTestUse, fit checks at Kennedy Space Center]
-
A.
isUsedToTest
chosen
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
B.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
-
C.
test
Indicates that an entity performs, undergoes, or is associated with a testing or examination process involving another entity or condition.
-
D.
testPilot
Indicates that an entity serves as a pilot responsible for testing and evaluating aircraft or related flight systems.
-
E.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e22c89081909b1ec0cd36a1ef45 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.