Triple
T29431698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McLaren 600LT |
E746448
|
entity |
| Predicate | platformBasedOn |
P17743
|
FINISHED |
| Object | McLaren 570S |
—
|
NE NERFINISHED |
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 570S | Statement: [McLaren 600LT, platformBasedOn, McLaren 570S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformBasedOn Context triple: [McLaren 600LT, platformBasedOn, McLaren 570S]
-
A.
platformUsed
Indicates that an action, event, or interaction was carried out using a particular platform (e.g., software, service, or system) as the medium or tool.
-
B.
platformUsedFor
Indicates that one entity serves as the platform, medium, or environment utilized to perform, host, or support the activities of another entity.
-
C.
platformFamily
chosen
Indicates that one platform belongs to, or is categorized under, a broader family or group of related platforms.
-
D.
platformAppearsOn
Indicates that a particular platform is present, visible, or available within or on another specified context, medium, or environment.
-
E.
usedPlatformType
Indicates that an entity makes use of or operates on a particular type or category of platform.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 3:13 p.m.