Triple
T25274537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National First Division club |
E633659
|
entity |
| Predicate | typicalHomeVenue |
P41695
|
FINISHED |
| Object | football stadium |
—
|
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: football stadium | Statement: [National First Division club, typicalHomeVenue, football stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHomeVenue Context triple: [National First Division club, typicalHomeVenue, football stadium]
-
A.
home venue type
chosen
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
-
B.
typicalAbode
Indicates the usual or characteristic place where an entity lives, resides, or is most commonly found.
-
C.
earlyHomeVenueFor
Indicates that one entity served as the primary home venue for another entity during an early or initial period of its existence or activity.
-
D.
typicalInterior
Indicates that one entity is the usual or characteristic interior of another entity.
-
E.
typicalHouse
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 21, 2026, 1:17 p.m.