Triple
T31324981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occitan (in Guardia Piemontese) |
E798857
|
entity |
| Predicate | localNameUsedIn |
P97559
|
FINISHED |
| Object | Guardia Piemontese |
—
|
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: Guardia Piemontese | Statement: [Occitan (in Guardia Piemontese), localNameUsedIn, Guardia Piemontese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localNameUsedIn Context triple: [Occitan (in Guardia Piemontese), localNameUsedIn, Guardia Piemontese]
-
A.
localNameDefinition
Indicates that an entity’s locally scoped name is defined or specified within a particular context or namespace.
-
B.
modernLocalName
Indicates the current, locally used name or designation for an entity, as recognized in the present time.
-
C.
hasNoWidelyUsedLocalName
Indicates that the entity does not have a commonly used or widely recognized name in the local language or region.
-
D.
currentNameUsedFrom
Indicates that an entity’s currently used name has been in effect starting from a specified point in time or source.
-
E.
notableLocalName
chosen
Indicates that an entity is known by a notable or commonly used local name within a specific region or community.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 9:15 p.m.