Triple
T11842346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fight of the Century (vs. Joe Frazier, 1971) |
E281682
|
entity |
| Predicate | hostArenaCapacityApprox |
P76907
|
FINISHED |
| Object | 20000 |
—
|
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: 20000 | Statement: [Fight of the Century (vs. Joe Frazier, 1971), hostArenaCapacityApprox, 20000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostArenaCapacityApprox Context triple: [Fight of the Century (vs. Joe Frazier, 1971), hostArenaCapacityApprox, 20000]
-
A.
hostArena
chosen
Indicates that one entity serves as the arena or venue where an event or activity involving the other entity takes place.
-
B.
approximateCapacity
Indicates that one entity has an estimated or rough capacity value relative to another or to a specified measure.
-
C.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
D.
arenaUsed
Indicates that a particular arena or venue is utilized or has been employed for a specific event, activity, or purpose.
-
E.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65a597c8190b09f57463b279afc |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.