Triple
T7814612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wildfire |
E180772
|
entity |
| Predicate | recordingArtistOccupation |
P50979
|
FINISHED |
| Object | American singer-songwriter |
—
|
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: American singer-songwriter | Statement: [Wildfire, recordingArtistOccupation, American singer-songwriter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingArtistOccupation Context triple: [Wildfire, recordingArtistOccupation, American singer-songwriter]
-
A.
artistOccupation
Indicates the professional role or job that an artist holds or performs.
-
B.
hasMainPerformerOccupation
chosen
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional role.
-
C.
mostFamousRecordingArtist
Indicates that the subject is the most famous recording artist associated with, or within the context of, the given entity.
-
D.
producerArtist
Indicates that one entity serves as the producer (e.g., overseeing or managing the creation) of a work created or performed by the artist entity.
-
E.
firstRecordingArtistRole
Indicates the role or capacity in which an artist first participated in a particular recording.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf96c009c81909726e1653b6f1348 |
completed | March 30, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:38 p.m.