Triple
T10681454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pesa |
E251764
|
entity |
| Predicate | hasBrand |
P1500
|
FINISHED |
| Object | Pesa Elf |
E251764
|
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: Pesa Elf | Statement: [Pesa, hasBrand, Pesa Elf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pesa Elf Context triple: [Pesa, hasBrand, Pesa Elf]
-
A.
Pesa
chosen
Pesa is a Polish manufacturer of rail vehicles, particularly known for producing modern trams and trains used in various European cities.
-
B.
Pesa
The Pesa is a river in Tuscany, central Italy, known for flowing through the Chianti region before joining the Arno.
-
C.
Pengo
Pengo is a Dravidian language spoken primarily by the Pengo people in parts of central India, especially in Odisha and neighboring regions.
-
D.
Penge
Penge is a suburban district in southeast London known for its Victorian architecture and proximity to Crystal Palace.
-
E.
Petlad
Petlad is a town in the Indian state of Gujarat, known for its agricultural markets and role as a local commercial center in the Anand region.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc30be481909922844b539b622d |
completed | April 9, 2026, 1:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d98885abf88190b54ed9db779d3ff0 |
completed | April 10, 2026, 11:32 p.m. |
Created at: April 8, 2026, 9:10 p.m.