Triple
T27772464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phenomenon (remix) |
E701784
|
entity |
| Predicate | sharesSongStructureWith |
P192908
|
FINISHED |
| Object | Phenomenon |
—
|
LITERAL FINISHED |
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: Phenomenon | Statement: [Phenomenon (remix), sharesSongStructureWith, Phenomenon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesSongStructureWith Context triple: [Phenomenon (remix), sharesSongStructureWith, Phenomenon]
-
A.
sharesSong
Indicates that one entity provides or distributes a song to another entity.
-
B.
sharesSongwritersWith
Indicates that two musical works have at least one songwriter in common.
-
C.
sharesMusicWith
Indicates that one entity provides or exchanges music with another entity.
-
D.
sharesInstrumentalWith
Indicates that two entities are associated with or use the same instrumental resource, tool, or means in performing an action or achieving a result.
-
E.
sharesTracksWith
Indicates that two entities have one or more tracks in common, such as shared audio, rail, or route segments.
- F. None of above. chosen
Provenance (4 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 27, 2026, 4:36 p.m.