Triple
T16132774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Stand (Colchester Community Stadium) |
E391441
|
entity |
| Predicate | hasHomeSupporterSectionStatus |
P49935
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [North Stand (Colchester Community Stadium), hasHomeSupporterSectionStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeSupporterSectionStatus Context triple: [North Stand (Colchester Community Stadium), hasHomeSupporterSectionStatus, true]
-
A.
hasHomeSupport
Indicates that an entity receives assistance, backing, or favorable conditions from its home environment or local supporters.
-
B.
hasSupporter
Indicates that one entity supports, endorses, or backs another entity.
-
C.
hasSupportersSection
chosen
Indicates that something includes a dedicated section or area specifically intended for its supporters.
-
D.
hasSupporterGroup
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
-
E.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a02e0048190b4e2c6ff434c2d7a |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.