Triple
T24092721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Brophy |
E596828
|
entity |
| Predicate | playingLevel |
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: [John Brophy, playingLevel, professional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playingLevel Context triple: [John Brophy, playingLevel, 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.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
C.
intendedPlayerLevel
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
D.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
E.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
- 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd20134881908b9ba6069a708a92 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:56 p.m.