Triple
T5488792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avestan script |
E123648
|
entity |
| Predicate | hasDistinctUpperLowerCase |
P64339
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Avestan script, hasDistinctUpperLowerCase, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctUpperLowerCase Context triple: [Avestan script, hasDistinctUpperLowerCase, false]
-
A.
hasUppercaseAndLowercase
Indicates that a string or text value contains at least one uppercase letter and at least one lowercase letter.
-
B.
hasDistinctLetters
Indicates that all letters in the given string or word are unique, with no character repeated.
-
C.
hasUppercase
Indicates that an entity contains at least one uppercase (capital) letter.
-
D.
hasDistinctCharacterSet
Indicates that two compared items use different sets of characters, with no character set being a subset or duplicate of the other.
-
E.
hasLowercaseLetters
Indicates that the referenced text contains at least one lowercase alphabetic character.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd93e4d2d081908eb75ee22fe72824 |
completed | March 20, 2026, 6:37 p.m. |
Created at: March 20, 2026, 2:10 p.m.