Triple
T27356554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATK Launch Systems |
E685700
|
entity |
| Predicate | providedComponentFor |
P1261
|
FINISHED |
| Object | Space Shuttle |
—
|
NE NERFINISHED |
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 Shuttle | Statement: [ATK Launch Systems, providedComponentFor, Space Shuttle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedComponentFor Context triple: [ATK Launch Systems, providedComponentFor, Space Shuttle]
-
A.
providedFor
chosen
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
B.
providedForExtension
Indicates that something is supplied or made available specifically to support or enable an extension of another thing (such as functionality, duration, or scope).
-
C.
componentFrom
Indicates that one entity is derived from, produced by, or originates as a component of another entity.
-
D.
otherComponentOf
Indicates that one entity is a different part or member of the same larger whole or system as another entity.
-
E.
developsComponentFor
Indicates that one entity creates or builds a component intended to be used by or within another entity.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 11:51 a.m.