Triple
T472513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shores of the Cosmic Ocean |
E8588
|
entity |
| Predicate | hasOpeningSequence |
P2827
|
FINISHED |
| Object | journey across the universe to Earth |
—
|
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: journey across the universe to Earth | Statement: [The Shores of the Cosmic Ocean, hasOpeningSequence, journey across the universe to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningSequence Context triple: [The Shores of the Cosmic Ocean, hasOpeningSequence, journey across the universe to Earth]
-
A.
hasTextOpening
chosen
Indicates that an entity begins with or contains a specified initial segment of text.
-
B.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
C.
openedBefore
Indicates that one entity was opened at an earlier time than another entity.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
openingInvocation
Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eff24108819092fdb85019ec4089 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.