Triple
T18737166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pré-Saint-Didier |
E458193
|
entity |
| Predicate | hasProvinceCode |
P3446
|
FINISHED |
| Object | AO |
—
|
NE NERFINISHED |
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: AO | Statement: [Pré-Saint-Didier, hasProvinceCode, AO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AO Context triple: [Pré-Saint-Didier, hasProvinceCode, AO]
-
A.
AO
AO is the two-letter ISO 3166-1 alpha-2 country code representing Angola in international standards and systems.
-
B.
AO
chosen
AO is the vehicle registration code used on license plates for vehicles registered in Italy’s Aosta Valley region.
-
C.
AO
AO is a UK-based online electricals retailer known for selling appliances and consumer electronics through its e-commerce platform and associated services.
-
D.
AO
AO was the foreign organization branch of the Nazi Party (NSDAP), responsible for coordinating and overseeing party activities among Germans living abroad.
-
E.
AO
AO is the regional vehicle registration code used on license plates for vehicles registered in the Khust area of Ukraine.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e57689fa508190ad821d361cba9edf |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 10, 2026, 11:51 a.m.