Triple
T5887248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stampede City |
E130893
|
entity |
| Predicate | hasNotableEventSeason |
P7547
|
FINISHED |
| Object | July |
—
|
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: July | Statement: [Stampede City, hasNotableEventSeason, July]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEventSeason Context triple: [Stampede City, hasNotableEventSeason, July]
-
A.
notableSeason
chosen
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
-
B.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
C.
hasPostseasonEvent
Indicates that an entity is associated with or participates in a postseason event, such as playoffs or championships, following a regular season.
-
D.
hasImportantSeason
Indicates that an entity experiences a particular season or time period that is especially significant or notable for it.
-
E.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
- 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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.