Triple
T16180943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MotoE World Championship |
E392680
|
entity |
| Predicate | startOfUseName |
P70850
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [MotoE World Championship, startOfUseName, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfUseName Context triple: [MotoE World Championship, startOfUseName, 2023]
-
A.
startUseBy
Indicates the point in time from which an entity begins to be used by another entity or for a particular purpose.
-
B.
usesNameSince
Indicates that an entity has been using a particular name continuously starting from a specified point in time.
-
C.
nameUsedSince
chosen
Indicates that a particular name has been in use for an entity starting from a specified point in time.
-
D.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
-
E.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205c92b48190b7125dbbcff3662e |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.