Triple
T36744871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troisvierges |
E907727
|
entity |
| Predicate | hasLuxembourgishName |
P45990
|
FINISHED |
| Object | Ëlwen |
—
|
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: Ëlwen | Statement: [Troisvierges, hasLuxembourgishName, Ëlwen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuxembourgishName Context triple: [Troisvierges, hasLuxembourgishName, Ëlwen]
-
A.
hasNameInLuxembourgish
chosen
Indicates that an entity is known or referred to by a specific name in the Luxembourgish language.
-
B.
hasNameInRomansh
Indicates that an entity is associated with a specific name or designation expressed in the Romansh language.
-
C.
hasOfficialNameInRomansh
Indicates that an entity has an official name expressed in the Romansh language.
-
D.
hasFranconianName
Indicates that an entity is associated with a name or designation in the Franconian language or dialect.
-
E.
hasNameInBelgium
Indicates that an entity is known or referred to by a particular name specifically within the context of Belgium.
- F. None of above.
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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.