Triple
T4741015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Stadium (Baltimore) |
E105239
|
entity |
| Predicate | capacityFootballApprox |
P13599
|
FINISHED |
| Object | over 60,000 |
—
|
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: over 60,000 | Statement: [Memorial Stadium (Baltimore), capacityFootballApprox, over 60,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityFootballApprox Context triple: [Memorial Stadium (Baltimore), capacityFootballApprox, over 60,000]
-
A.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a stadium can accommodate.
-
B.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
C.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
D.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
E.
typeOfFootball
Indicates the specific code or variant of football that characterizes or classifies a given football-related entity.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a5f3548190a6acf1dcfd64d11d |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.