Triple
T6260958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorking Wanderers F.C. |
E140295
|
entity |
| Predicate | homeGroundCapacitySeated |
P3507
|
FINISHED |
| Object | approximately 500 |
—
|
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: approximately 500 | Statement: [Dorking Wanderers F.C., homeGroundCapacitySeated, approximately 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundCapacitySeated Context triple: [Dorking Wanderers F.C., homeGroundCapacitySeated, approximately 500]
-
A.
homeStadiumCapacity
chosen
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
B.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
C.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
D.
typicalSeatingCapacityUpperBound
Indicates the maximum number of seats that a venue or vehicle is typically designed or allowed to accommodate under normal conditions.
-
E.
typicalSeatingCapacityLowerBound
Indicates the minimum number of seats that an entity is typically designed or expected to provide.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063856f308190a351a661caaae5f9 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.