Triple
T2160478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isuzu |
E47989
|
entity |
| Predicate | hasModel |
P2390
|
FINISHED |
| Object | Isuzu N-Series |
E47989
|
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: Isuzu N-Series | Statement: [Isuzu, hasModel, Isuzu N-Series]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Isuzu N-Series Context triple: [Isuzu, hasModel, Isuzu N-Series]
-
A.
Isuzu
chosen
Isuzu is a Japanese automotive manufacturer best known for producing commercial vehicles, pickup trucks, and diesel engines for global markets.
-
B.
Hino
Hino is a town in Shiga Prefecture, Japan, known for its historical streetscapes and traditional industries.
-
C.
Hino
Hino is a city in western Tokyo, Japan, known as a residential and industrial suburb within the Tama area.
-
D.
Toyota Hilux
The Toyota Hilux is a globally popular, highly durable pickup truck renowned for its reliability and off-road capability.
-
E.
Merkur XR4Ti
The Merkur XR4Ti is a mid-1980s, turbocharged rear-wheel-drive sport hatchback sold by Ford’s short-lived Merkur brand in North America, based on the European Ford Sierra.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8894d481908eda9363fd36fea6 |
completed | March 7, 2026, 5:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae58e9ceb08190871ff9c57ece23c0 |
completed | March 9, 2026, 5:21 a.m. |
Created at: March 4, 2026, 7:45 p.m.