Triple
T11317391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmic Call 1999 |
E268000
|
entity |
| Predicate | containsMessageType |
P640
|
FINISHED |
| Object | digital data |
—
|
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: digital data | Statement: [Cosmic Call 1999, containsMessageType, digital data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMessageType Context triple: [Cosmic Call 1999, containsMessageType, digital data]
-
A.
hasKeyMessage
Indicates that one entity conveys, contains, or is associated with a primary or central message of another entity.
-
B.
hasContentType
chosen
Indicates that an entity is associated with or classified by a specific type of content.
-
C.
precedesMessageType
Indicates that one message type must occur or be processed before another specified message type.
-
D.
relatedMessageType
Indicates that one message is associated with another by specifying the type or category of that related message.
-
E.
hasMessageSender
Indicates that one entity is the sender or originator of a given message.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c3cf748190987838029d9f7fff |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.