Triple
T30174228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pat Mastelotto |
E767005
|
entity |
| Predicate | startTimeOfNotableTenure |
P34618
|
FINISHED |
| Object | joined King Crimson in 1994 |
—
|
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: joined King Crimson in 1994 | Statement: [Pat Mastelotto, startTimeOfNotableTenure, joined King Crimson in 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfNotableTenure Context triple: [Pat Mastelotto, startTimeOfNotableTenure, joined King Crimson in 1994]
-
A.
notableManagerTenureStart
Indicates the date or point in time when a manager’s particularly significant or distinguished period of managing an entity began.
-
B.
timeInOfficeBeginsIn
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
C.
startTimeOfNotableRole
chosen
Indicates the point in time when an entity began a notable role, position, or function.
-
D.
officeHolderStartTime
Indicates the date and time at which an individual begins holding a particular office or position.
-
E.
termStartAsChancellor
Indicates the date or point in time when an individual begins their term serving in the role of chancellor.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: April 29, 2026, 7:25 p.m.