Triple
T5387700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington–Grizzly Stadium |
E120241
|
entity |
| Predicate | hasRecordCrowd |
P15029
|
FINISHED |
| Object | crowds exceeding listed capacity |
—
|
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: crowds exceeding listed capacity | Statement: [Washington–Grizzly Stadium, hasRecordCrowd, crowds exceeding listed capacity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordCrowd Context triple: [Washington–Grizzly Stadium, hasRecordCrowd, crowds exceeding listed capacity]
-
A.
hasCrowdLevel
Indicates the degree or intensity of how crowded a place, event, or situation is.
-
B.
hasAudienceSize
chosen
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
C.
crowdWas
Indicates that a crowd possessed or exhibited a particular state, quality, or condition.
-
D.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
E.
haveSpeakerPopulation
Indicates that an entity has a specified number or population size of people who speak a particular language.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f8d81081909174027a4fe640f2 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.