Triple
T5214643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (NCC-1701-A) |
E117721
|
entity |
| Predicate | starshipType |
P3141
|
FINISHED |
| Object | Federation heavy cruiser |
—
|
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: Federation heavy cruiser | Statement: [USS Enterprise (NCC-1701-A), starshipType, Federation heavy cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starshipType Context triple: [USS Enterprise (NCC-1701-A), starshipType, Federation heavy cruiser]
-
A.
starshipRegistry
Indicates a formal registration relationship where a starship is recorded in an official registry or database.
-
B.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
-
C.
featuresSpacecraft
Indicates that one entity includes, presents, or prominently involves a spacecraft as part of its content, composition, or subject matter.
-
D.
starVehicleFor
Indicates that one entity serves as the primary or featured vehicle associated with another entity, such as a person, production, or event.
-
E.
stellarClass
Indicates the spectral classification relationship between a star and its stellar class (e.g., O, B, A, F, G, K, M).
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a928dfc8190971a9e28d5c10446 |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.