Triple
T25618241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Yze |
E642216
|
entity |
| Predicate | laterWorkPeriod |
P173194
|
FINISHED |
| Object | 2010s (assistant coaching) |
—
|
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: 2010s (assistant coaching) | Statement: [Adam Yze, laterWorkPeriod, 2010s (assistant coaching)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterWorkPeriod Context triple: [Adam Yze, laterWorkPeriod, 2010s (assistant coaching)]
-
A.
laterWork
Indicates that one work was created, published, or produced after another work in time.
-
B.
laterWorkBy
Indicates that one work was created after another work by the same creator or author.
-
C.
afterAWorkBy
Indicates that one work is created subsequent to and based on, inspired by, or derived from another existing work.
-
D.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
-
E.
workAfter
Indicates that one entity performs its work or begins an activity only after another specified entity has completed or started its own work.
- F. None of above. chosen
Provenance (4 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 21, 2026, 5:02 p.m.