Triple
T13749607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Alphabet |
E330306
|
entity |
| Predicate | hasLetterMeaning |
P47684
|
FINISHED |
| Object | A means Allah |
—
|
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: A means Allah | Statement: [Supreme Alphabet, hasLetterMeaning, A means Allah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLetterMeaning Context triple: [Supreme Alphabet, hasLetterMeaning, A means Allah]
-
A.
letterMeaning
chosen
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
B.
hasLastThreeLettersMeaning
Indicates that the last three letters of one entity (typically a word or string) together form a meaningful unit or have a specific semantic significance.
-
C.
lettersMeaning
Indicates that a set of letters or characters represents, signifies, or conveys a particular meaning or message.
-
D.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
E.
hasLiteralMeaning
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02148c208190a882927905a861a6 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:08 p.m.