Triple
T924330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonas |
E19949
|
entity |
| Predicate | languageFormOf |
P6281
|
FINISHED |
| Object | Hebrew name Yonah |
—
|
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: Hebrew name Yonah | Statement: [Jonas, languageFormOf, Hebrew name Yonah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFormOf Context triple: [Jonas, languageFormOf, Hebrew name Yonah]
-
A.
languageForm
chosen
Indicates the specific linguistic form or expression in which something is conveyed or represented.
-
B.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
C.
isWorkingLanguageOf
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
D.
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).
-
E.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3296f50819087f809fbe90b139e |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.