Triple
T23494194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Feehily |
E571656
|
entity |
| Predicate | yearsActiveAsMusician |
P18004
|
FINISHED |
| Object | 1990s–present |
—
|
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: 1990s–present | Statement: [Mark Feehily, yearsActiveAsMusician, 1990s–present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearsActiveAsMusician Context triple: [Mark Feehily, yearsActiveAsMusician, 1990s–present]
-
A.
timeInArtistCareer
Indicates the point or period within an artist’s professional career at which a given event, work, or activity occurs.
-
B.
playedWithBandUntil
Indicates that an individual was a member of and performed with a specific band up to a certain end time or date.
-
C.
activeYearsInCareer
chosen
Indicates the span of time during which an entity was actively engaged in a particular career or professional field.
-
D.
activeInYears
Indicates that an entity was active or operational during the specified years or year range.
-
E.
workedAsSessionMusicianFor
Indicates that one entity performed as a session musician providing musical services or recordings for another entity, typically an artist, band, or production.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7de1ab88190b6c2441c63a99713 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.