Triple
T24429112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dingoes Ate My Baby |
E615941
|
entity |
| Predicate | basedOnRealBand |
P155887
|
FINISHED |
| Object | Four Star Mary |
—
|
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: Four Star Mary | Statement: [Dingoes Ate My Baby, basedOnRealBand, Four Star Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnRealBand Context triple: [Dingoes Ate My Baby, basedOnRealBand, Four Star Mary]
-
A.
usesBand
Indicates that one entity employs or makes use of a particular band (such as a group, frequency band, or band resource) in performing an action or fulfilling a function.
-
B.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
C.
hasOriginBand
Indicates that an entity (such as a musician or musical act) is or was originally a member of a specified band.
-
D.
playedWithBandFrom
Indicates that an individual has performed as a member or guest with a musical band originating from a specified place or organization.
-
E.
hasBackingBand
Indicates that an artist or performer is supported musically by a specific band that plays instruments or accompaniment for them.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a983d88190904b559694363a19 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:15 a.m.