Triple
T21704875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster Yamaha Tech3 |
E535746
|
entity |
| Predicate | endedAssociationYear |
P133441
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Monster Yamaha Tech3, endedAssociationYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedAssociationYear Context triple: [Monster Yamaha Tech3, endedAssociationYear, 2018]
-
A.
hasAssociatedYear
Indicates that an entity is linked to a specific year that is relevant to it (e.g., creation, occurrence, or reference year).
-
B.
associatedClassYear
Indicates a relationship linking an entity to the specific academic class year with which it is connected or identified.
-
C.
yearAssociated
chosen
Indicates a specific year that is relevant or linked to an entity, event, or relationship (such as the year it occurred, was created, or is otherwise associated).
-
D.
relatedYear
Indicates a connection between an entity and a specific year that is relevant to its occurrence, validity, or significance.
-
E.
ordinationYear
Indicates the year in which an individual was formally ordained to a religious office or role.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb52e4b84819095a24cc9fdca2b8a |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.