Triple
T25824912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland State Fairgrounds |
E650501
|
entity |
| Predicate | notableEventSeason |
P88968
|
FINISHED |
| Object | late summer |
—
|
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: late summer | Statement: [Maryland State Fairgrounds, notableEventSeason, late summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventSeason Context triple: [Maryland State Fairgrounds, notableEventSeason, late summer]
-
A.
seasonOfNotableEvent
chosen
Indicates the season of the year during which a notable event occurs or is recognized.
-
B.
notableSeason
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
-
C.
seasonHighlightEvent
Indicates an event that stands out as a key or notable highlight within a particular season.
-
D.
game1NotableEvent
Indicates that a specific event is recognized as a notable or significant occurrence within the context of game1.
-
E.
notableEventTeam
Indicates a team that is significantly associated with, or played a key role in, a particular notable event.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 22, 2026, 7:32 a.m.