Triple
T15086706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyli municipality |
E360292
|
entity |
| Predicate | hasAdministrativeSeat |
P1474
|
FINISHED |
| Object | Pyli |
E360288
|
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: Pyli | Statement: [Pyli municipality, hasAdministrativeSeat, Pyli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyli Context triple: [Pyli municipality, hasAdministrativeSeat, Pyli]
-
A.
Pyli
chosen
Pyli is a town in central Greece known as a gateway to the Pindus mountains and the wider Trikala region.
-
B.
Piyassili
Piyassili was a Hittite prince and military leader, known for governing Syrian territories such as Carchemish under his father, King Suppiluliuma I.
-
C.
Piro
Piro is an alternate name for the Yine language, an indigenous Arawakan language spoken in Peru.
-
D.
Piro
Piro is a town in the Bhojpur district of Bihar, India, known as one of the district’s principal urban and commercial centers.
-
E.
Pylia
Pylia is a figure in Greek mythology known primarily as the mother of Aegeus, the legendary king of Athens and father of Theseus.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00276d1608190bc310d5b86ecd1d5 |
completed | April 15, 2026, 9:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae1ba4208190b1e8c55668a1b422 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:03 a.m.