Triple
T36115193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Sports 800 |
E1044598
|
entity |
| Predicate | approximateProduction |
P99700
|
FINISHED |
| Object | about 3131 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: about 3131 units | Statement: [Toyota Sports 800, approximateProduction, about 3131 units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateProduction Context triple: [Toyota Sports 800, approximateProduction, about 3131 units]
-
A.
approximateProductionNumber
chosen
Indicates that one entity specifies an estimated or non-exact quantity associated with the production output of another entity.
-
B.
productionStartApproximate
Indicates that the start of production for something is known only approximately rather than as an exact date or time.
-
C.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
-
D.
designedApproximately
Indicates that one entity was created, planned, or engineered to an estimated or imprecise degree in relation to another entity or specification.
-
E.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:08 p.m.