Triple
T13784567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Stadium at Hollywood Park |
E331219
|
entity |
| Predicate | proposedCapacityType |
P4139
|
FINISHED |
| Object | large-capacity stadium |
—
|
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: large-capacity stadium | Statement: [Los Angeles Stadium at Hollywood Park, proposedCapacityType, large-capacity stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedCapacityType Context triple: [Los Angeles Stadium at Hollywood Park, proposedCapacityType, large-capacity stadium]
-
A.
hasCapacityType
chosen
Indicates that an entity possesses a specific kind or classification of capacity or capability.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
-
D.
currentCapacity
Indicates the present amount of capacity an entity is using or able to provide at a given time.
-
E.
expandedCapacity
Indicates that an entity’s capacity has been increased beyond its previous or standard level.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0248db988190aa43c3723af25f90 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.