Triple
T28671285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Picard |
E725724
|
entity |
| Predicate | relatedDialectGroup |
P78566
|
FINISHED |
| Object | Norman |
—
|
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: Norman | Statement: [Old Picard, relatedDialectGroup, Norman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDialectGroup Context triple: [Old Picard, relatedDialectGroup, Norman]
-
A.
relatedDialect
chosen
Indicates that one dialect has a recognized linguistic relationship or close affinity to another dialect.
-
B.
relatedDialectArea
Indicates that one dialect area is geographically, historically, or linguistically connected to another dialect area.
-
C.
associatedWithDialectGroup
Indicates that one entity is connected or related to a particular dialect group, typically through usage, origin, or classification.
-
D.
commonInDialectGroup
Indicates that something (such as a word, form, or feature) is frequently used or widely found within a particular dialect group.
-
E.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a005247dba08190acadf962bcefe4a0 |
completed | May 10, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_6a00519029848190a234358dfba45084 |
completed | May 10, 2026, 9:36 a.m. |
Created at: April 28, 2026, 5:03 a.m.