Triple
T14741804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mick Doohan’s Motocoaster |
E346365
|
entity |
| Predicate | hasLaunch |
P115586
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mick Doohan’s Motocoaster, hasLaunch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunch Context triple: [Mick Doohan’s Motocoaster, hasLaunch, yes]
-
A.
hasLaunchedFor
Indicates that an entity (such as a product, feature, or service) has been officially released or made available specifically for another entity (such as a user, group, market, or platform).
-
B.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
-
C.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
D.
hasLaunchHistoryEvent
Indicates that there exists a recorded event in the launch history associated with the given entity.
-
E.
launchedTo
Indicates that one entity has been sent or propelled from its origin toward a specific target or destination.
- F. None of above. chosen
Provenance (4 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7367a1c819081082cc355e385fa |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.