Triple
T29779733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jealous One's Envy |
E755478
|
entity |
| Predicate | placeOfOriginOfSound |
P161922
|
FINISHED |
| Object | Bronx, New York City |
—
|
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: Bronx, New York City | Statement: [Jealous One's Envy, placeOfOriginOfSound, Bronx, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfOriginOfSound Context triple: [Jealous One's Envy, placeOfOriginOfSound, Bronx, New York City]
-
A.
isSoundProducedBy
Indicates that a particular sound is generated or emitted by a specified source or entity.
-
B.
placeOfRecording
Indicates the location where an audio, video, or other recording was made.
-
C.
placeOfOrigin
Indicates the location or source from which an entity originally comes or was created.
-
D.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
-
E.
showcasesSoundOf
chosen
Indicates that one entity presents or highlights the characteristic sound produced 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 8:49 p.m.