Triple
T9363332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austro-Hungarian Navy |
E225332
|
entity |
| Predicate | headquartersLocation |
P62
|
FINISHED |
| Object | Pola |
E195064
|
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: Pola | Statement: [Austro-Hungarian Navy, headquartersLocation, Pola]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pola Context triple: [Austro-Hungarian Navy, headquartersLocation, Pola]
-
A.
Pola
chosen
Pola is a historic coastal city on the Istrian Peninsula, known today as Pula in Croatia and famed for its well-preserved Roman amphitheater.
-
B.
Poldi
Poldi is a common German diminutive nickname for the given name Leopold.
-
C.
Polkemmet
Polkemmet is a locality in Scotland best known for the former Polkemmet Country Park and its historic estate grounds.
-
D.
POLIN
POLIN is a modern museum in Warsaw dedicated to preserving and presenting the thousand-year history and culture of Jews in Poland.
-
E.
Poli
Poli is a small town in northern Cameroon that serves as an administrative and local trading center within the country's North 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd503ddf8c81908b090afa54ec5e6d |
completed | April 1, 2026, 5:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0f3eaf2208190967a3a8e82a4070b |
completed | April 4, 2026, 11:20 a.m. |
Created at: March 30, 2026, 7:42 p.m.