Triple
T16515869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta Legends |
E401181
|
entity |
| Predicate | playedLastGameInYear |
P123852
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Atlanta Legends, playedLastGameInYear, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedLastGameInYear Context triple: [Atlanta Legends, playedLastGameInYear, 2019]
-
A.
lastGamePlayed
Indicates the most recent game that an entity has participated in or played.
-
B.
lastSeasonAsSingleGame
Indicates that the referenced season is the final one in which the subject participated as a single, standalone game (before any change in format, structure, or grouping).
-
C.
previousMatchYear
Indicates that one event or match occurred in the year immediately preceding the year of another event or match.
-
D.
lastGameSeason
Indicates that one entity is the final or most recent game season associated with another entity.
-
E.
laterPlayedFor
Indicates that an individual was a member of or played for a team or organization at a time after a previously referenced team or organization.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7bbfa481909037148cdb4d8996 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.