Triple
T11820419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Dunn |
E281109
|
entity |
| Predicate | ledLeagueInWalks |
P2218
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Adam Dunn, ledLeagueInWalks, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledLeagueInWalks Context triple: [Adam Dunn, ledLeagueInWalks, 2008]
-
A.
ledLeagueIn
chosen
Indicates that an entity achieved the highest performance or total in a specified statistical category within a particular league for a given season or time period.
-
B.
ledLeague
Indicates that an entity finished a season or competition as the statistical leader of a specified category within a particular league.
-
C.
ledTeamIn
Indicates that one entity had primary leadership responsibility over a team in which the other entity participated or was involved.
-
D.
ledTeamTo
Indicates that one entity acted as a leader or guiding force that directed a team toward achieving a particular goal, outcome, or success.
-
E.
walksLeader
Indicates that one entity walks at the front and leads another entity during movement.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e87e488190905bc3bb6d721e56 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.