Triple
T16637250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Tigers (franchise lineage) |
E404240
|
entity |
| Predicate | operatedAsLondonTigersFrom |
P4445
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [London Tigers (franchise lineage), operatedAsLondonTigersFrom, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsLondonTigersFrom Context triple: [London Tigers (franchise lineage), operatedAsLondonTigersFrom, 1989]
-
A.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
-
B.
operatedAs
chosen
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
C.
foundedAsFisherCats
Indicates that an organization or team was originally established under the name "Fisher Cats."
-
D.
notableTeamOperated
Indicates that an entity is or was operated, managed, or run by a team that is considered notable or significant.
-
E.
laterOperatedUnder
Indicates that an entity, after an earlier period, was subsequently managed, controlled, or conducted under a different name, organization, framework, or operational context.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378ea4b848190bf7c95dad8a855f0 |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.