Triple
T19683120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shed End |
E472642
|
entity |
| Predicate | hasHomeFans |
P136905
|
FINISHED |
| Object | Chelsea FC 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: Chelsea FC fans | Statement: [Shed End, hasHomeFans, Chelsea FC fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeFans Context triple: [Shed End, hasHomeFans, Chelsea FC fans]
-
A.
hasHomeFansNickname
Indicates that an entity is known by a particular nickname specifically used by its home fans.
-
B.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
C.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
-
D.
hasFanBaseDepictedAs
Indicates that an entity has a fan base that is visually or narratively represented in some form (e.g., in media, artwork, or documentation).
-
E.
hasFanBasePrimarilyIn
Indicates that an entity’s main or largest group of supporters, followers, or fans is located in a specified place or region.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641c126b88190820281058a1e7793 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:45 p.m.