Triple
T8060035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie Howe |
E188095
|
entity |
| Predicate | startTimeAtClubLabel |
P69890
|
FINISHED |
| Object | AFC Bournemouth (first permanent appointment as manager) |
—
|
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: AFC Bournemouth (first permanent appointment as manager) | Statement: [Eddie Howe, startTimeAtClubLabel, AFC Bournemouth (first permanent appointment as manager)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAtClubLabel Context triple: [Eddie Howe, startTimeAtClubLabel, AFC Bournemouth (first permanent appointment as manager)]
-
A.
clubForStartTime
Indicates the time at which a club-related event or activity is scheduled to begin.
-
B.
managementStartAtClub
chosen
Indicates the time or date when an individual begins their managerial role at a specific club.
-
C.
clubForEndTime
Indicates the time at which a club-related event, activity, or association comes to an end.
-
D.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
E.
startTimeWithTeam
Indicates the time at which an activity, event, or engagement begins in association with a specific team.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcaa8b8819099267564b6542547 |
completed | March 31, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.