Triple
T101381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish English |
E2046
|
entity |
| Predicate | regionallyVaried |
P1762
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
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: yes | Statement: [Irish English, regionallyVaried, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallyVaried Context triple: [Irish English, regionallyVaried, yes]
-
A.
regionalDialect
chosen
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
B.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
C.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2563921f8819087f720b1c803579f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.