Triple
T20086668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teddington Cricket Club |
E496149
|
entity |
| Predicate | longEstablished |
P55641
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Teddington Cricket Club, longEstablished, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longEstablished Context triple: [Teddington Cricket Club, longEstablished, true]
-
A.
longLived
Indicates that an entity has a lifespan or duration of existence significantly longer than what is typical or expected in its context.
-
B.
isLongStanding
chosen
Indicates that a relationship, condition, or state has existed for a considerable or extended period of time.
-
C.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
D.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
E.
longType
Indicates that something has a length-related classification or is characterized by being of extended duration or distance.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655ba40c8190adea0e271a1249cf |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:04 p.m.