Triple
T33967496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Sobrante |
E870893
|
entity |
| Predicate | succeededByInBand |
P200848
|
FINISHED |
| Object | Tré Cool |
—
|
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: Tré Cool | Statement: [Al Sobrante, succeededByInBand, Tré Cool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByInBand Context triple: [Al Sobrante, succeededByInBand, Tré Cool]
-
A.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential order.
-
B.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
C.
succeededByContext
Indicates that one context or situation directly follows and replaces another in a sequence or progression.
-
D.
succeededBy (TX-11)
chosen
Indicates that one entity directly follows and replaces another in a sequence, order, or succession.
-
E.
succeedsBy
Indicates that one entity comes after or replaces another in a sequence, order, or position.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:50 a.m.