Triple
T8861041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dvin |
E210886
|
entity |
| Predicate | otherHistoricalLanguagesSpoken |
P29176
|
FINISHED |
| Object | 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: Greek | Statement: [Dvin, otherHistoricalLanguagesSpoken, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherHistoricalLanguagesSpoken Context triple: [Dvin, otherHistoricalLanguagesSpoken, Greek]
-
A.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
B.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
C.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
D.
historicalLanguageRegion
chosen
Indicates that a language was historically spoken or used within a particular geographic region, regardless of its current status there.
-
E.
heritageLanguage
Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e860888190a8a8702377db949e |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.