Triple
T33829050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Stand |
E867044
|
entity |
| Predicate | servesSupportersOf |
P49046
|
FINISHED |
| Object | Hibernian supporters |
—
|
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: Hibernian supporters | Statement: [West Stand, servesSupportersOf, Hibernian supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesSupportersOf Context triple: [West Stand, servesSupportersOf, Hibernian supporters]
-
A.
usedBySupporters
chosen
Indicates that something is utilized or employed by supporters of a person, group, cause, or entity.
-
B.
associatedWithSupporters
Indicates that an entity has a relationship or connection with individuals or groups who support or advocate for it.
-
C.
hasSupportersIn
Indicates that an entity is backed or endorsed by people or groups located within a specified place or region.
-
D.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
-
E.
supporters
Indicates a relationship where one entity backs, endorses, or actively helps another entity, cause, or position.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
Created at: May 1, 2026, 1:46 a.m.