Triple
T34803521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newmarket Royals |
E1003283
|
entity |
| Predicate | operatedInOHLFrom |
P202226
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Newmarket Royals, operatedInOHLFrom, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInOHLFrom Context triple: [Newmarket Royals, operatedInOHLFrom, 1992]
-
A.
historicallyOperatedIn
Indicates that an entity carried out its activities or operations within a particular location or context during a past time period.
-
B.
historicallyOperatedOn
Indicates that an entity has, at some point in the past, performed an operation or action upon another entity.
-
C.
operatedInLeagueFrom
chosen
Indicates that an entity participated or competed in a particular league starting from a specified time.
-
D.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
E.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a00d820a7788190a8d54625cd87be68 |
completed | May 10, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_6a00d7c5b40c8190b80413238d04e81e |
completed | May 10, 2026, 7:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.