Triple
T25246901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Katunich |
E632629
|
entity |
| Predicate | activeYearsWithIncubus |
P143955
|
FINISHED |
| Object | early years of the band |
—
|
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: early years of the band | Statement: [Alex Katunich, activeYearsWithIncubus, early years of the band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeYearsWithIncubus Context triple: [Alex Katunich, activeYearsWithIncubus, early years of the band]
-
A.
activeInYears
Indicates that an entity was active or operational during the specified years or year range.
-
B.
activeYearsWith
chosen
Indicates the span of time during which an entity was actively engaged in a particular role, activity, or association with another entity.
-
C.
managedYearsWithAngels
Indicates the number of years an entity has served in a managerial role with the Angels organization.
-
D.
activeYearsPeak
Indicates the span of years during which an entity was at the height of its activity or prominence.
-
E.
activeInYear
Indicates that an entity was active, functioning, or operational during a specified year.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48086e9088190b8a78f3665a7a25b |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:10 p.m.