Triple
T1515239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estadio Akron |
E32103
|
entity |
| Predicate | inauguralMatchDate |
P26158
|
FINISHED |
| Object | 2010-07-30 |
—
|
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: 2010-07-30 | Statement: [Estadio Akron, inauguralMatchDate, 2010-07-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inauguralMatchDate Context triple: [Estadio Akron, inauguralMatchDate, 2010-07-30]
-
A.
inauguralSeason
Indicates the first season in which an entity (such as a team, league, or event) officially began participating or operating.
-
B.
finalMatchDate
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
-
C.
inauguralMLSMatchResult
Indicates the outcome or result of an entity’s first-ever match in Major League Soccer.
-
D.
inauguralHolderStartDate
Indicates the date on which the first person or entity to hold a position, title, or role officially began their tenure.
-
E.
inauguralEventDate
chosen
Indicates the calendar date on which an entity’s first or inaugural event took place.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9396e16408190b5e7b0ac43376d81 |
completed | March 5, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69a907aa67cc81909f00135365447399 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.