Triple
T28533678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPIC |
E722105
|
entity |
| Predicate | originalSpacecraftConcept |
P38461
|
FINISHED |
| Object | Triana |
—
|
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: Triana | Statement: [EPIC, originalSpacecraftConcept, Triana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSpacecraftConcept Context triple: [EPIC, originalSpacecraftConcept, Triana]
-
A.
spaceConcept
Indicates a conceptual or abstract relationship involving space, such as spatial properties, structures, or organizational principles, rather than specific physical locations or objects.
-
B.
mainSpacecraft
Indicates that one spacecraft is designated as the primary or principal spacecraft in relation to another entity or context.
-
C.
spacecraftOrigin
Indicates the place or source from which a spacecraft was originally launched, built, or sent.
-
D.
spacecraftModel
chosen
Indicates that one entity is the specific model or design type of a spacecraft associated with another entity.
-
E.
spacecraft
Indicates that an entity is a vehicle or object designed to travel or operate in outer space.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: April 28, 2026, 3:30 a.m.