Triple
T14986236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yehuda |
E373707
|
entity |
| Predicate | hasISO15924ScriptCode |
P11937
|
FINISHED |
| Object | Hebr |
—
|
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: Hebr | Statement: [Yehuda, hasISO15924ScriptCode, Hebr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO15924ScriptCode Context triple: [Yehuda, hasISO15924ScriptCode, Hebr]
-
A.
hasISO15924Number
Indicates that an entity (a writing script) is associated with a specific numeric code defined by the ISO 15924 standard.
-
B.
scriptCodeISO15924
chosen
Indicates the script or writing system used to represent text, identified by its ISO 15924 code.
-
C.
hasUnicodeScript
Indicates that a character or text element belongs to a specific Unicode script category (such as Latin, Cyrillic, or Han).
-
D.
ISO15924Status
Indicates the official status or classification of a script according to the ISO 15924 standard.
-
E.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7007588819095bb1de029a6f2eb |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:52 a.m.