Triple
T32902495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Song to the Evening Star |
E841647
|
entity |
| Predicate | associatedKeyCharacter |
P198125
|
FINISHED |
| Object | Wolfram |
E76334
|
NE 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: Wolfram | Statement: [Song to the Evening Star, associatedKeyCharacter, Wolfram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedKeyCharacter Context triple: [Song to the Evening Star, associatedKeyCharacter, Wolfram]
-
A.
associatedKey
Indicates that one entity serves as a key or identifier that is logically or functionally linked to another entity.
-
B.
areKeyTo
Indicates that something is essential or critically important for enabling, achieving, or understanding something else.
-
C.
keyAssociation
Indicates an associative relationship where one entity serves as a key used to identify, access, or link to another entity or set of entities.
-
D.
keyOfficialAssociated
Indicates that an entity is formally connected to or designated as a primary or principal official for another entity or context.
-
E.
hasCharacterAssociated
chosen
Indicates that one entity is linked to or connected with a particular character (such as a person, figure, or persona) in some relevant way.
- F. None of above.
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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34c692d8d481909f05bf78f4f1a6e7 |
completed | June 19, 2026, 4:33 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:19 a.m.