Triple
T3832519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Car of the Year |
E91045
|
entity |
| Predicate | jurorProfession |
P52259
|
FINISHED |
| Object | motoring journalist |
—
|
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: motoring journalist | Statement: [European Car of the Year, jurorProfession, motoring journalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jurorProfession Context triple: [European Car of the Year, jurorProfession, motoring journalist]
-
A.
juryProvidedBy
Indicates that a particular jury is supplied, appointed, or made available by a specified source or authority.
-
B.
legalProfessionRole
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
C.
notableJuryMember
Indicates that an entity served as a distinguished or noteworthy member of a particular jury or judging panel.
-
D.
juryComposition
Indicates the relationship specifying how a jury is constituted, including the number, type, or characteristics of its members.
-
E.
courtRole
Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8787bc8190819a7af975b609df |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:17 p.m.