Triple
T11330783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota 4Runner |
E268336
|
entity |
| Predicate | offersTrim |
P55815
|
FINISHED |
| Object | TRD Pro |
E619362
|
NE 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: TRD Pro | Statement: [Toyota 4Runner, offersTrim, TRD Pro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TRD Pro Context triple: [Toyota 4Runner, offersTrim, TRD Pro]
-
A.
TRD Pro
chosen
TRD Pro is an off-road-focused performance trim level offered by Toyota, featuring enhanced suspension, rugged styling, and specialized equipment for improved capability on rough terrain.
-
B.
TRD
TRD is the IATA airport code for Trondheim Airport, Værnes, the main international airport serving Trondheim, Norway.
-
C.
TRG
TRG is the IATA airport code for Tauranga Airport in Tauranga, New Zealand.
-
D.
TRZ
TRZ is the stock ticker symbol for Trizec Properties, a former publicly traded real estate investment trust focused on commercial office properties.
-
E.
TRZ
TRZ is the IATA airport code for Tiruchirappalli International Airport, a major air gateway serving the city of Tiruchirappalli in the Indian state of Tamil Nadu.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fd38308190a5458be1bfcc89ea |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e526236b688190aca4f2400a12e726 |
completed | April 19, 2026, 6:59 p.m. |
Created at: April 8, 2026, 9:32 p.m.