Triple
T27026066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shammua |
E680786
|
entity |
| Predicate | hasOriginalScriptForm |
P126570
|
FINISHED |
| Object | שַׁמּוּעַ |
—
|
NE NERFINISHED |
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: שַׁמּוּעַ | Statement: [Shammua, hasOriginalScriptForm, שַׁמּוּעַ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalScriptForm Context triple: [Shammua, hasOriginalScriptForm, שַׁמּוּעַ]
-
A.
hasOriginalWritingSystem
Indicates that an entity possesses or is associated with a primary, native, or first-developed writing system used to represent its language or content.
-
B.
hasOriginalCharacter
Indicates that an entity includes, features, or is associated with an original character distinct from pre-existing or canonical characters.
-
C.
hasOriginalScriptName
Indicates that an entity is associated with the name of its script or title as it appears in the original language or writing system.
-
D.
hasOriginalTitleScript
chosen
Indicates that an entity’s original title is written or represented in a specific writing system or script.
-
E.
hasGraphemeShapeOrigin
Indicates that one grapheme’s shape is derived or originates from the shape of another grapheme or graphical form.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 7:11 a.m.