Triple
T35707487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FINAL PE |
E1031756
|
entity |
| Predicate | belongsToAlphabet |
P20857
|
FINISHED |
| Object | Hebrew alphabet |
—
|
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 alphabet | Statement: [FINAL PE, belongsToAlphabet, Hebrew alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToAlphabet Context triple: [FINAL PE, belongsToAlphabet, Hebrew alphabet]
-
A.
relatedAlphabet
Indicates that two entities are connected through a relationship involving their positions, order, or correspondence within an alphabet or alphabetical system.
-
B.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
C.
alphabeticPartRepresents
Indicates that the alphabetic portion of an identifier, code, or label stands for or denotes a particular concept, category, or entity.
-
D.
alphabetic
Indicates that the characters in a string or sequence consist solely of letters from an alphabet, with no digits or special symbols.
-
E.
alphabet
chosen
Indicates that one entity is an alphabet or set of symbols used for representing elements (such as characters or tokens) in relation to another entity.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
Created at: May 3, 2026, 4:05 p.m.