Triple
T2641787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kippax Stand |
E62882
|
entity |
| Predicate | homeSupportersSectionFor |
P42456
|
FINISHED |
| Object | Manchester City F.C. fans |
—
|
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: Manchester City F.C. fans | Statement: [Kippax Stand, homeSupportersSectionFor, Manchester City F.C. fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeSupportersSectionFor Context triple: [Kippax Stand, homeSupportersSectionFor, Manchester City F.C. fans]
-
A.
homeSection
Indicates that something belongs to, is part of, or is designated as the primary/home section within a larger structure or collection.
-
B.
homeSectionName
Indicates the designated name or label assigned to a particular section of a home or homepage.
-
C.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
D.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
-
E.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
- 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8fdc0bc8190b7fd102b87ee50d1 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:53 p.m.