Triple
T16266619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motor Trend SUV of the Year |
E394890
|
entity |
| Predicate | judgingProcess |
P64965
|
FINISHED |
| Object | road testing |
—
|
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: road testing | Statement: [Motor Trend SUV of the Year, judgingProcess, road testing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgingProcess Context triple: [Motor Trend SUV of the Year, judgingProcess, road testing]
-
A.
judgedBy
Indicates that one entity evaluates, assesses, or forms an opinion about another entity, often in an official or critical capacity.
-
B.
judgedOn
Indicates that an entity is evaluated or assessed based on a specified criterion, standard, or aspect.
-
C.
judgesSelectionMethod
chosen
Indicates that a judge or judging body uses a particular method or criteria to evaluate and select among options or candidates.
-
D.
judgesAre
Indicates that one entity serves as a judge or evaluator of another entity.
-
E.
judgeSelectionAuthority
Indicates that an entity has the authority or responsibility to select, appoint, or choose judges for a given role or position.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c839788190b974d1d0d2525b88 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.