Triple
T26873412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donovan Morgan |
E676677
|
entity |
| Predicate | hasPlayedForLevel |
P39395
|
FINISHED |
| Object | professional |
—
|
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: professional | Statement: [Donovan Morgan, hasPlayedForLevel, professional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayedForLevel Context triple: [Donovan Morgan, hasPlayedForLevel, professional]
-
A.
playedAtLevel
chosen
Indicates that an entity participated or performed in an activity, event, or game at a specified level of difficulty, competition, or hierarchy.
-
B.
hasBeenPlayedAt
Indicates that an entity (such as a song, track, or media item) has been performed or broadcast at a particular time, place, or event.
-
C.
hasBeenPlayedIn
Indicates that an entity (such as a song, video, or game) has been previously played or performed within a particular context or medium.
-
D.
wasPlayed
Indicates that an entity (such as a game, song, or media item) was performed, executed, or used by someone or something.
-
E.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 5:34 a.m.