Triple
T29901564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reading FC |
E759418
|
entity |
| Predicate | hasClubCrestFeature |
P118883
|
FINISHED |
| Object | royal crown |
—
|
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: royal crown | Statement: [Reading FC, hasClubCrestFeature, royal crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClubCrestFeature Context triple: [Reading FC, hasClubCrestFeature, royal crown]
-
A.
teamEmblem
chosen
Indicates that an emblem (such as a logo or symbol) represents or is officially associated with a particular team.
-
B.
primaryClubColorsVisible
Indicates that the primary colors associated with a club are clearly visible or prominently displayed.
-
C.
hasClubColor
Indicates that a club or team is associated with a specific color or set of colors used to represent it.
-
D.
hasClanSymbol
Indicates that an entity is associated with a particular clan through a specific identifying symbol.
-
E.
competitionLogo
Indicates that one entity serves as the official logo or emblem representing a particular competition.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 6:06 p.m.