Triple
T23455724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the scribes |
E567916
|
entity |
| Predicate | languageOfTextsHandled |
P73048
|
FINISHED |
| Object | Hebrew |
—
|
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 | Statement: [the scribes, languageOfTextsHandled, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfTextsHandled Context triple: [the scribes, languageOfTextsHandled, Hebrew]
-
A.
recognizesLanguages
chosen
Indicates that an entity has the ability to identify, understand, or acknowledge one or more languages.
-
B.
languageOfTranslations
Indicates that one entity is the language into which another entity (such as a text or work) has been translated.
-
C.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
D.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
E.
languageOfWorkRecognized
Indicates that a work is officially recognized as being created or expressed in a particular 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a696e6c48190a7159292cfe3362f |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.