Triple
T32544953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Eerie |
E831818
|
entity |
| Predicate | previousProjectOfCreator |
P52195
|
FINISHED |
| Object | The Microphones |
—
|
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: The Microphones | Statement: [Mount Eerie, previousProjectOfCreator, The Microphones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousProjectOfCreator Context triple: [Mount Eerie, previousProjectOfCreator, The Microphones]
-
A.
previousWorkByProducer
Indicates that a work was created earlier by the same producer responsible for another referenced work.
-
B.
parentProject
Indicates that one project serves as the direct higher-level or containing project in relation to another project.
-
C.
predecessorProject
chosen
Indicates that one project temporally or logically comes before and leads into another project in a sequence or dependency chain.
-
D.
previousWorkByArtist
Indicates that the related work was created earlier by the same artist as the current or reference work.
-
E.
previousCollaboration
Indicates that the entities have worked together or collaborated on something in the past.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:02 a.m.