Triple
T32675777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Nova Scotia |
E835427
|
entity |
| Predicate | hasOfficialFrenchName |
P181088
|
FINISHED |
| Object | Ordre de la Nouvelle-Écosse |
—
|
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: Ordre de la Nouvelle-Écosse | Statement: [Order of Nova Scotia, hasOfficialFrenchName, Ordre de la Nouvelle-Écosse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialFrenchName Context triple: [Order of Nova Scotia, hasOfficialFrenchName, Ordre de la Nouvelle-Écosse]
-
A.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
-
B.
hasOfficialNameInLatin
Indicates that an entity has an official or formally recognized name expressed in the Latin language.
-
C.
hasOfficialNameInRomansh
Indicates that an entity has an official name expressed in the Romansh language.
-
D.
hasOfficialShortNameInEnglish
Indicates that an entity has a designated official short form of its name expressed in English.
-
E.
hasOfficialNameInFinnish
Indicates that an entity has a specific official name expressed in the Finnish 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: May 1, 2026, 1:09 a.m.