Triple
T35752073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus F1 Team |
E1033344
|
entity |
| Predicate | constructorEntryName |
P194577
|
FINISHED |
| Object | Lotus-Renault |
—
|
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: Lotus-Renault | Statement: [Lotus F1 Team, constructorEntryName, Lotus-Renault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorEntryName Context triple: [Lotus F1 Team, constructorEntryName, Lotus-Renault]
-
A.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
B.
constantName
Indicates that an entity has a specific, fixed identifier or label used as a constant within a system or context.
-
C.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
D.
CWEName
Indicates that an entity is identified or labeled by a specific Common Weakness Enumeration (CWE) name.
-
E.
usedConstructorName
Indicates that a particular constructor was invoked using a specific constructor name in the creation or initialization of an entity.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fd7b042a548190b3abe31bc3258278 |
completed | May 8, 2026, 5:56 a.m. |
Created at: May 3, 2026, 4:06 p.m.