Triple
T21308889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (NCC-1701-B) |
E525275
|
entity |
| Predicate | encounteredPhenomenon |
P143678
|
FINISHED |
| Object | Nexus energy ribbon |
—
|
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: Nexus energy ribbon | Statement: [USS Enterprise (NCC-1701-B), encounteredPhenomenon, Nexus energy ribbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounteredPhenomenon Context triple: [USS Enterprise (NCC-1701-B), encounteredPhenomenon, Nexus energy ribbon]
-
A.
examplePhenomenon
Indicates a representative or illustrative occurrence used to demonstrate or clarify a broader phenomenon or pattern.
-
B.
capturesPhenomenon
Indicates that one entity records, represents, or effectively reflects the occurrence or characteristics of a particular phenomenon.
-
C.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
-
D.
demonstratedPhenomenon
Indicates that an entity has shown, exhibited, or provided evidence for the occurrence of a particular phenomenon.
-
E.
allegedPhenomenon
Indicates that something is claimed or reported to be a phenomenon, but its existence, cause, or nature is uncertain or disputed.
- F. None of above. chosen
Provenance (4 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa916548190a11f8bb4255e3fed |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:06 p.m.