Triple
T36626461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLF Runway 15 |
E904180
|
entity |
| Predicate | primaryUserDuringShuttleProgram |
P204976
|
FINISHED |
| Object | Space Shuttle program |
E5108
|
NE 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: Space Shuttle program | Statement: [SLF Runway 15, primaryUserDuringShuttleProgram, Space Shuttle program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUserDuringShuttleProgram Context triple: [SLF Runway 15, primaryUserDuringShuttleProgram, Space Shuttle program]
-
A.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
B.
primaryUserDesignation
Indicates that one user is designated as the main or primary user among multiple associated users.
-
C.
primaryPassengerGroup
Indicates the main group of passengers that is most directly associated with or served by a given entity or context.
-
D.
roleInSpaceShipOneProgram
Indicates that an entity has a specific role or involvement in the SpaceShipOne program.
-
E.
primaryUserPosition
Indicates the main or default spatial or role-based position assigned to a user within a given context or system.
- F. None of above. chosen
Provenance (5 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a094f846081908bb1b326d061f6f1 |
completed | June 23, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.