Triple
T32728928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Expectations (single release) |
E836894
|
entity |
| Predicate | hasNamesakeTrack |
P63063
|
FINISHED |
| Object | Great Expectations (song) |
—
|
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: Great Expectations (song) | Statement: [Great Expectations (single release), hasNamesakeTrack, Great Expectations (song)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeTrack Context triple: [Great Expectations (single release), hasNamesakeTrack, Great Expectations (song)]
-
A.
hasNamesakeFeature
Indicates that one entity has a feature (such as a place, object, or structure) that is named after another entity.
-
B.
hasEarlierNamesake
Indicates that an entity shares its name with another entity that existed earlier in time.
-
C.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
D.
hasMusicalAlias
Indicates that an entity is known or performs under an alternative musical name or stage name.
-
E.
hasTitleNamesake
chosen
Indicates that one entity serves as the namesake or source of the title borne by another entity.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 1, 2026, 1:11 a.m.