Triple
T9709562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seneca nation |
E234986
|
entity |
| Predicate | playsTraditionalGame |
P13828
|
FINISHED |
| Object | Lacrosse |
—
|
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: Lacrosse | Statement: [Seneca nation, playsTraditionalGame, Lacrosse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsTraditionalGame Context triple: [Seneca nation, playsTraditionalGame, Lacrosse]
-
A.
traditionalGame
chosen
Indicates that the relationship involves playing, practicing, or being associated with a game that is rooted in longstanding cultural or historical traditions.
-
B.
gamePlayed
Indicates that a particular game is or was played by an entity (such as a person, team, or group) during a specific event or time.
-
C.
cityGame6
Indicates a relationship where an entity is associated with a specific city-based game, event, or competition labeled as variant 6.
-
D.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
E.
clubGamesFor
Indicates a relationship where a player participates in games on behalf of a specific club.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da7c6188190b086f7e411378268 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.