Triple
T15970143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AESA |
E387296
|
entity |
| Predicate | advantageOver |
P635
|
FINISHED |
| Object | PESA |
E845646
|
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 | Statement: [AESA, advantageOver, PESA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PESA Context triple: [AESA, advantageOver, PESA]
-
A.
Pesa
Pesa is a Polish manufacturer of rail vehicles, particularly known for producing modern trams and trains used in various European cities.
-
B.
Pesa
chosen
The Pesa is a river in Tuscany, central Italy, known for flowing through the Chianti region before joining the Arno.
-
C.
PSE
PSE is the national stock exchange of the Philippines, providing a marketplace for the trading of securities such as stocks and bonds.
-
D.
PSE
PSE is the station code for Porto São Bento, a historic and centrally located railway station in Porto, Portugal.
-
E.
PSE
PSE is a major European political party alliance that brings together socialist, social democratic, and labor parties from across the European Union.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e157291214819088d65e984609e42c |
completed | April 16, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3c5a7d48190891e69314e67e9af |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:54 a.m.