Triple
T31878930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imagine (John Lennon album, selected tracks) |
E813822
|
entity |
| Predicate | featuresSelectionsFrom |
P16786
|
FINISHED |
| Object | Imagine |
—
|
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: Imagine | Statement: [Imagine (John Lennon album, selected tracks), featuresSelectionsFrom, Imagine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSelectionsFrom Context triple: [Imagine (John Lennon album, selected tracks), featuresSelectionsFrom, Imagine]
-
A.
featuresSamplesFrom
Indicates that one entity includes or incorporates sample elements originating from another entity.
-
B.
featuresSample
Indicates that an entity includes or presents a particular sample as one of its components or examples.
-
C.
selectionFrom
chosen
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
-
D.
selectionCharacteristic
Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
-
E.
featuresEnsembleFrom
Indicates that something includes or presents an ensemble that originates from or is derived from another source.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
Created at: April 30, 2026, 11:56 p.m.