Triple
T35277030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | So Much (for) Stardust |
E1018826
|
entity |
| Predicate | spokenWordPerformer |
P139866
|
FINISHED |
| Object | Ethan Hawke |
—
|
NE NERFINISHED |
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: Ethan Hawke | Statement: [So Much (for) Stardust, spokenWordPerformer, Ethan Hawke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenWordPerformer Context triple: [So Much (for) Stardust, spokenWordPerformer, Ethan Hawke]
-
A.
notableSpokenWordPerformer
Indicates that the subject is a well-known or distinguished performer in spoken word, such as poetry, storytelling, or similar verbal performance arts.
-
B.
spokenWord
Indicates that one entity has uttered or articulated a specific word or phrase in spoken form.
-
C.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
D.
performedTextBy
chosen
Indicates that a text-based work (such as a script, lyrics, or written piece) is realized or executed as a performance by a specific performer or group.
-
E.
performerDescribedAs
Indicates that a performer is characterized or referred to using a particular description, label, or role.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fa6d6a88190a2e8ba972c9697d0 |
completed | May 3, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.