Triple
T10650930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin NCAP |
E250965
|
entity |
| Predicate | rates |
P29104
|
FINISHED |
| Object | adult occupant protection |
—
|
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: adult occupant protection | Statement: [Latin NCAP, rates, adult occupant protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rates Context triple: [Latin NCAP, rates, adult occupant protection]
-
A.
rate
chosen
Indicates the numerical evaluation or assessment assigned by one entity to another based on perceived quality, performance, or value.
-
B.
rateDefinition
Indicates that one entity specifies or defines the rate or ratio at which another entity changes, is applied, or is measured.
-
C.
baseRate
Indicates the fundamental or standard rate at which something occurs or is charged, serving as a baseline before adjustments or modifiers are applied.
-
D.
symbolRates
Indicates a quantitative rate or value associated with a given symbol in relation to another reference (such as time, currency, or unit).
-
E.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff6ba688190b493689d60f616e0 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.