Triple
T9146578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Foxes |
E219471
|
entity |
| Predicate | relatedToCrest |
P37
|
FINISHED |
| Object | fox on Leicester City F.C. badge |
—
|
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: fox on Leicester City F.C. badge | Statement: [The Foxes, relatedToCrest, fox on Leicester City F.C. badge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToCrest Context triple: [The Foxes, relatedToCrest, fox on Leicester City F.C. badge]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
relatedToProduct
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
-
D.
relatedToProject
Indicates that an entity has a connection or association with a specific project, without specifying the exact nature of that involvement.
-
E.
relatedToClaimOf
Indicates a relationship where something is connected or pertinent to a specific claim or assertion.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca917914c8190b97ca9169bbd1e5e |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.