Triple
T7501588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commune d’Avully |
E177272
|
entity |
| Predicate | governs |
P760
|
FINISHED |
| Object | Avully |
E33266
|
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: Avully | Statement: [Commune d’Avully, governs, Avully]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Avully Context triple: [Commune d’Avully, governs, Avully]
-
A.
Avully
chosen
Avully is a small Swiss municipality located in the canton of Geneva, near the French border.
-
B.
Avul
Avul is a given name most notably associated with Avul Pakir Jainulabdeen Abdul Kalam, the former President of India and renowned aerospace scientist.
-
C.
Ululayu
Ululayu is another name for Shalmaneser V, an Assyrian king of the 8th century BCE known for his campaigns in the Levant and the siege of Samaria.
-
D.
Shushary
Shushary is a municipal settlement in the southern part of Saint Petersburg, Russia, known for its residential areas and industrial facilities.
-
E.
Avusy
Avusy is a small rural municipality located in the canton of Geneva in southwestern Switzerland, near the French border.
- 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_69c69f2696688190915a8458f2398211 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f59aabb8819085bdbe9c793d5b8b |
completed | March 27, 2026, 9:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c84608021481908ce58a131d75188b |
completed | March 28, 2026, 9:20 p.m. |
Created at: March 27, 2026, 3:44 p.m.