Triple
T33367194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granges-Paccot |
E854385
|
entity |
| Predicate | localName_rm |
P97559
|
FINISHED |
| Object | Granges-Paccot |
—
|
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: Granges-Paccot | Statement: [Granges-Paccot, localName_rm, Granges-Paccot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localName_rm Context triple: [Granges-Paccot, localName_rm, Granges-Paccot]
-
A.
modernLocalName
Indicates the current, locally used name or designation for an entity, as recognized in the present time.
-
B.
localNameDefinition
Indicates that an entity’s locally scoped name is defined or specified within a particular context or namespace.
-
C.
lessCommonNameFor
Indicates that the subject is a less commonly used name or label for the same entity or concept as the object.
-
D.
rootName
Indicates that the referenced node serves as the primary or top-level root in a hierarchical structure or dependency tree.
-
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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:35 a.m.