Triple
T27343518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantis (OV-104) |
E684170
|
entity |
| Predicate | spaceShuttleFleet |
P60879
|
FINISHED |
| Object | Space Shuttle orbiter fleet |
—
|
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 orbiter fleet | Statement: [Atlantis (OV-104), spaceShuttleFleet, Space Shuttle orbiter fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceShuttleFleet Context triple: [Atlantis (OV-104), spaceShuttleFleet, Space Shuttle orbiter fleet]
-
A.
SpaceShuttleOrbiter
Indicates that an entity functions as a space shuttle orbiter, specifically the reusable winged spacecraft component of a space shuttle system.
-
B.
spaceShuttleFlight
Indicates a specific mission or journey undertaken by a space shuttle between launch and landing.
-
C.
orbiterFleet
chosen
Indicates that one entity is part of, or belongs to, a fleet of orbiting spacecraft associated with another entity.
-
D.
relatedSpacecraft
Indicates that there is an association or connection between two spacecraft, such as shared mission, design, origin, or operational relationship.
-
E.
spacecraftCount
Indicates the number of spacecraft associated with a given entity or context.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 11:44 a.m.