Triple
T24224507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stewart Grand Prix |
E601553
|
entity |
| Predicate | constructorWin |
P155263
|
FINISHED |
| Object | 1999 European Grand Prix |
—
|
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: 1999 European Grand Prix | Statement: [Stewart Grand Prix, constructorWin, 1999 European Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorWin Context triple: [Stewart Grand Prix, constructorWin, 1999 European Grand Prix]
-
A.
windowType
Indicates the specific kind or category of window associated with an entity.
-
B.
constructedUnder
Indicates that something was built, created, or assembled while subject to the authority, direction, or conditions imposed by a particular agent, rule, plan, or regime.
-
C.
testWindow
Indicates that an entity functions as, or is associated with, a specific window used for testing or experimental purposes.
-
D.
constructedAs
Indicates that one entity is built, formed, or created in the manner, structure, or configuration specified by another entity.
-
E.
constructedInside
Indicates that one entity was built or assembled within the physical boundaries of another 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287ddfecc81909f5396857974bc8c |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, midnight