Triple
T17153174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Workington Town R.L.F.C. |
E416272
|
entity |
| Predicate | hasHomeStadiumCapacityApprox |
P3507
|
FINISHED |
| Object | 10000 |
—
|
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: 10000 | Statement: [Workington Town R.L.F.C., hasHomeStadiumCapacityApprox, 10000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeStadiumCapacityApprox Context triple: [Workington Town R.L.F.C., hasHomeStadiumCapacityApprox, 10000]
-
A.
homeStadiumCapacity
chosen
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
B.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
C.
cityStadiumCapacity
Indicates the maximum number of spectators that a given city’s stadium can accommodate.
-
D.
hasTeamStadium
Indicates that a sports team is associated with or plays its home games at a particular stadium.
-
E.
formerStadiumCapacityApprox
Indicates that an entity’s past stadium capacity is approximately equal to the given number, rather than an exact figure.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f4092c40819096359ff90af16c3e |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.