Triple
T35752113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus F1 Team |
E1033344
|
entity |
| Predicate | constructorPolesTotal |
P194876
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Lotus F1 Team, constructorPolesTotal, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorPolesTotal Context triple: [Lotus F1 Team, constructorPolesTotal, 2]
-
A.
typicalNumberOfPoleHandlers
Indicates the usual or standard number of handlers involved in managing or operating a pole in the given context.
-
B.
hasPoleAt
Indicates that one entity possesses, contains, or is associated with a pole located at a specific point or position.
-
C.
estimatedNumberOfPolesResettledFromEast
Indicates the estimated count of Polish people who were relocated or resettled from the eastern regions.
-
D.
poleDetermination
Indicates the process or result of establishing which pole or polarity is assigned to, associated with, or characterizes an entity in a given context.
-
E.
shaftCount
Indicates the number of shafts associated with or contained in an object or system.
- 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_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: May 3, 2026, 4:06 p.m.