Triple
T35572958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megarians |
E1027992
|
entity |
| Predicate | spokeDialect |
P1762
|
FINISHED |
| Object | Doric Greek |
—
|
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: Doric Greek | Statement: [Megarians, spokeDialect, Doric Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokeDialect Context triple: [Megarians, spokeDialect, Doric Greek]
-
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.
dialectStatus
Indicates the status or classification of a language variety as a dialect within a broader linguistic system.
-
C.
dialectDocumentation
Indicates that there exists documentation or descriptive information specifically about a particular dialect or dialectal variety.
-
D.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language or region.
-
E.
isSpokenAs
Indicates that one entity is used as the spoken or verbal form of another entity (e.g., a word, name, or phrase).
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.