Triple
T16181816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Car of the Year |
E392699
|
entity |
| Predicate | juryOrigin |
P52260
|
FINISHED |
| Object | various European countries |
—
|
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: various European countries | Statement: [European Car of the Year, juryOrigin, various European countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: juryOrigin Context triple: [European Car of the Year, juryOrigin, various European countries]
-
A.
juryProvidedBy
Indicates that a particular jury is supplied, appointed, or made available by a specified source or authority.
-
B.
jurorOrigin
chosen
Indicates the place or source (such as geographic location or jurisdiction) from which a juror is drawn or selected.
-
C.
juryIncludes
Indicates that a particular person or entity is a member of, or is included in, a specified jury.
-
D.
juryComposition
Indicates the relationship specifying how a jury is constituted, including the number, type, or characteristics of its members.
-
E.
juryRole
Indicates that an entity serves in the capacity or function of a juror within a judicial or decision-making process.
- F. None of above.
Provenance (3 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205d858c8190802d44e08e3cdcd6 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.