Triple
T6343820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode Hebrew block |
E142695
|
entity |
| Predicate | encodesScript |
P14248
|
FINISHED |
| Object | Hebrew script |
—
|
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 script | Statement: [Unicode Hebrew block, encodesScript, Hebrew script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodesScript Context triple: [Unicode Hebrew block, encodesScript, Hebrew script]
-
A.
encodes
chosen
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
-
B.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
C.
addsScript
Indicates that one entity attaches or incorporates a script (code or instructions) into another entity, enabling additional behavior or functionality.
-
D.
replacedScript
Indicates that one script has been substituted for or superseded by another script.
-
E.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0674702d08190806ef0998960b797 |
completed | March 22, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.