Triple
T25041624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilltop Hoods |
E627128
|
entity |
| Predicate | recordLabelFoundedBy |
P142493
|
FINISHED |
| Object | Golden Era Records |
—
|
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: Golden Era Records | Statement: [Hilltop Hoods, recordLabelFoundedBy, Golden Era Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordLabelFoundedBy Context triple: [Hilltop Hoods, recordLabelFoundedBy, Golden Era Records]
-
A.
recordLabelFounded
Indicates that a particular record label was established or created by a specific founder or founding entity.
-
B.
recordLabelTypeFounded
Indicates that a particular type or category of record label was established or came into existence on a specific date or in a specific time period.
-
C.
recordedForLabelFoundedBy
chosen
Indicates that an entity (such as an artist or band) recorded for a record label that was founded by a specified person or entity.
-
D.
recordLabelHeadquartersOf
Indicates that a particular location serves as the main headquarters of a specific record label.
-
E.
ownedRecordLabel
Indicates that one entity previously possessed legal ownership or controlling interest in a particular record label.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:08 a.m.