Triple
T34202549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montfort-sur-Meu |
E877425
|
entity |
| Predicate | hasNameInGallo |
P198608
|
FINISHED |
| Object | Monfort-sur-Meu |
—
|
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: Monfort-sur-Meu | Statement: [Montfort-sur-Meu, hasNameInGallo, Monfort-sur-Meu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInGallo Context triple: [Montfort-sur-Meu, hasNameInGallo, Monfort-sur-Meu]
-
A.
hasGalicianName
Indicates that an entity is associated with a name expressed in the Galician language.
-
B.
hasNameInOccitan
Indicates that an entity is associated with a specific name expressed in the Occitan language.
-
C.
hasNameInInnu
Indicates that an entity is known by a specific name expressed in the Innu language.
-
D.
hasNameInGreek
Indicates that an entity is associated with a specific representation of its name in the Greek language.
-
E.
hasNameInGeEz
Indicates that an entity is associated with a specific name written in the Geʽez script or language.
- F. None of above. chosen
Provenance (4 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
| PDg | Predicate description generation | batch_69fef5cec8208190b85665ab6a511a08 |
completed | May 9, 2026, 8:52 a.m. |
Created at: May 1, 2026, 1:55 a.m.