Triple
T13856813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisses |
E333086
|
entity |
| Predicate | hasDemonym |
P191
|
FINISHED |
| Object | Lissoise |
E1066917
|
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: Lissoise | Statement: [Lisses, hasDemonym, Lissoise]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lissoise Context triple: [Lisses, hasDemonym, Lissoise]
-
A.
Lissois
chosen
Lissois is the French demonym for inhabitants of the commune of Lisses in the Île-de-France region.
-
B.
Lisse
Lisse is a town in the western Netherlands renowned for its flower bulb fields and the famous Keukenhof gardens.
-
C.
Lisses
Lisses is a commune in the southern suburbs of Paris, located in the Essonne department in the Île-de-France region of northern France.
-
D.
Libná
Libná is a small settlement that forms part of the town of Teplice nad Metují in the Hradec Králové Region of the Czech Republic.
-
E.
Lusei
Lusei are a major clan of the Mizo people of Northeast India, historically influential in shaping Mizo culture, language, and social organization.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c70a59e8819090b750699993a107 |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:14 p.m.