Triple
T31872324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of the Greek Interpreter |
E813640
|
entity |
| Predicate | languageOfKeyCharacter |
P200786
|
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: [The Adventure of the Greek Interpreter, languageOfKeyCharacter, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfKeyCharacter Context triple: [The Adventure of the Greek Interpreter, languageOfKeyCharacter, Greek]
-
A.
languageOfKeyText
Indicates that a specified language is the primary language in which a given key or central text is written.
-
B.
languageOfLetters
Indicates that one entity is the language in which the other entity’s letters or written correspondence are composed.
-
C.
isCharacterInWorkLanguage
Indicates that a character appears in a work (e.g., book, film, game) in a specific language version or localization.
-
D.
hasLanguageCharacter
Indicates that an entity uses, contains, or is associated with a specific written or symbolic character from a language.
-
E.
languageCharacterizedBy
Indicates that a language is defined or distinguished by a particular feature, property, or characteristic.
- F. None of above. chosen
Provenance (4 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
| PDg | Predicate description generation | batch_69ffacdea2408190949dba9edeca4412 |
completed | May 9, 2026, 9:53 p.m. |
Created at: April 30, 2026, 11:55 p.m.