Triple
T4769023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atbash |
E105879
|
entity |
| Predicate | alphabetRequirement |
P58668
|
FINISHED |
| Object | requires ordered 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: requires ordered alphabet | Statement: [Atbash, alphabetRequirement, requires ordered alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alphabetRequirement Context triple: [Atbash, alphabetRequirement, requires ordered alphabet]
-
A.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
B.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
C.
legalCharacter
Indicates that an entity possesses a status, role, or nature that is recognized and defined by law.
-
D.
hasLetterCount
Indicates that an entity is associated with a specific number representing how many letters it contains.
-
E.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
- F. None of above. chosen
Provenance (4 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:21 p.m.