Triple
T18203229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancia Delta S4 |
E435841
|
entity |
| Predicate | competitionEnd |
P130205
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [Lancia Delta S4, competitionEnd, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionEnd Context triple: [Lancia Delta S4, competitionEnd, 1986]
-
A.
competitionResult
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
-
B.
competitionStatus
Indicates the current state or phase of a competition, such as whether it is upcoming, ongoing, paused, or completed.
-
C.
competitionElement
Indicates that one entity is a component, phase, or sub-event within a larger competitive event or contest.
-
D.
competitionTiming
Indicates the temporal relationship or scheduling of when a competition or competitive event takes place.
-
E.
competitionBegan
Indicates that a competitive event or contest has started.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e221bbbc819088a7559a46b7d4e7 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:32 a.m.