Triple
T12060300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curved Dash Oldsmobile |
E287148
|
entity |
| Predicate | estimatedProduction |
P99700
|
FINISHED |
| Object | over 19,000 units |
—
|
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: over 19,000 units | Statement: [Curved Dash Oldsmobile, estimatedProduction, over 19,000 units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedProduction Context triple: [Curved Dash Oldsmobile, estimatedProduction, over 19,000 units]
-
A.
totalProduction
Indicates the overall quantity of goods, services, or output produced by an entity or system over a specified period or within a defined scope.
-
B.
approximateProductionNumber
chosen
Indicates that one entity specifies an estimated or non-exact quantity associated with the production output of another entity.
-
C.
increasesProductionOf
Indicates that one entity causes a rise or enhancement in the amount or rate at which another entity is produced.
-
D.
peakProductionRate
Indicates the maximum rate at which something can be produced over a given period under specified conditions.
-
E.
productionOutcome
Indicates the result or consequence produced by a given production process, activity, or event.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.