Triple
T29647778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McLaren GT |
E756049
|
entity |
| Predicate | unveilingEvent |
P29853
|
FINISHED |
| Object | McLaren standalone launch event in 2019 |
—
|
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: McLaren standalone launch event in 2019 | Statement: [McLaren GT, unveilingEvent, McLaren standalone launch event in 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unveilingEvent Context triple: [McLaren GT, unveilingEvent, McLaren standalone launch event in 2019]
-
A.
reunveiledOn
Indicates that something was revealed or made publicly known again on a specific date or occasion.
-
B.
unveiledAs
Indicates that one entity is revealed, presented, or disclosed in the role, identity, or form of another entity.
-
C.
introductionEvent
chosen
Indicates an event in which one entity is formally presented or made known to another entity or audience for the first time.
-
D.
portraysEvent
Indicates that one entity depicts, represents, or illustrates a particular event.
-
E.
unveiledBy
Indicates that something (such as an object, artwork, or project) was formally revealed or presented to the public by a particular agent or entity.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66ed3d37c81909b3e973fb9dd70cc |
completed | May 2, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:50 p.m.