Triple
T19683069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelsea Pitch Owners PLC |
E472640
|
entity |
| Predicate | hasMottoOrAim |
P29651
|
FINISHED |
| Object | to keep Chelsea at Stamford Bridge |
—
|
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: to keep Chelsea at Stamford Bridge | Statement: [Chelsea Pitch Owners PLC, hasMottoOrAim, to keep Chelsea at Stamford Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrAim Context triple: [Chelsea Pitch Owners PLC, hasMottoOrAim, to keep Chelsea at Stamford Bridge]
-
A.
usesMotto
chosen
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
B.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
C.
definesMotto
Indicates that one entity establishes or specifies the official motto associated with another entity.
-
D.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
E.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
- 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_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. |
Created at: April 10, 2026, 1:45 p.m.