Triple
T8311002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarasicodissa |
E194588
|
entity |
| Predicate | adoptedLanguageForCourt |
P6495
|
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: [Tarasicodissa, adoptedLanguageForCourt, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedLanguageForCourt Context triple: [Tarasicodissa, adoptedLanguageForCourt, Greek]
-
A.
adoptedLanguage
Indicates that an entity has chosen and begun using a particular language, typically as its official, primary, or preferred means of communication.
-
B.
languageOfJurisdiction
Indicates the language officially used for legal and administrative purposes within a given jurisdiction.
-
C.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
D.
courtLanguage
chosen
Indicates the language officially used in legal proceedings or by a court.
-
E.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2eecb08190ae0ba8adbaf58c8f |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.