Triple
T4292636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stradey Park |
E99631
|
entity |
| Predicate | hasStandingCapacity |
P55258
|
FINISHED |
| Object | about 6,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: about 6,000 | Statement: [Stradey Park, hasStandingCapacity, about 6,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandingCapacity Context triple: [Stradey Park, hasStandingCapacity, about 6,000]
-
A.
hasCapacityTo
Indicates that one entity possesses the ability, power, or potential to perform an action or bring about a particular effect in relation to another entity or context.
-
B.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
C.
heldByInCapacityAs
Indicates that something is held or possessed by an entity specifically in a defined role, function, or official capacity rather than in a general or personal sense.
-
D.
hasOccupancyStatus
Indicates the current usage or availability state of something, such as whether it is occupied, vacant, or otherwise in use.
-
E.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
- F. None of above. chosen
Provenance (4 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3508035a08190b752c8edce0aff86 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:08 p.m.