Triple
T27544336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WE League |
E695319
|
entity |
| Predicate | stadiumRequirement |
P162685
|
FINISHED |
| Object | meets JFA facility standards |
—
|
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: meets JFA facility standards | Statement: [WE League, stadiumRequirement, meets JFA facility standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stadiumRequirement Context triple: [WE League, stadiumRequirement, meets JFA facility standards]
-
A.
stadiumFeature
Indicates that a stadium possesses or includes a particular feature, characteristic, or facility.
-
B.
stadium
Indicates that an entity is a sports or event venue where games, competitions, or large gatherings take place.
-
C.
containsStadium
Indicates that a location or area includes a stadium within its boundaries or premises.
-
D.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
E.
cityStadiumCapacity
Indicates the maximum number of spectators that a given city’s stadium can accommodate.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f83176c81909a508c03229dc69d |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 1:32 p.m.