Triple
T25806002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herman Rarebell |
E649969
|
entity |
| Predicate | startTimeInBand_Scorpions |
P175193
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [Herman Rarebell, startTimeInBand_Scorpions, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeInBand_Scorpions Context triple: [Herman Rarebell, startTimeInBand_Scorpions, 1977]
-
A.
startTimeInBand_IronMaiden
Indicates the time at which an entity (such as a performance, membership, or event) begins within the context of the band Iron Maiden.
-
B.
startTimeInBand_Interpol
Indicates that the start time of an event or interval falls within a specified time band, with the exact value determined by interpolation.
-
C.
startTimeInBand_Metallica
Indicates the time at which Metallica began performing or being active within a specified time band or interval.
-
D.
startTimeInBand(The Clash)
Indicates the time at which The Clash began being an active member of the band.
-
E.
startTimeInBandSaxon
Indicates that an entity’s start time falls within a specified time band defined according to the Saxon (XPath/XQuery) date-time handling conventions.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 22, 2026, 7:03 a.m.