Triple
T27870956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pollard script |
E704488
|
entity |
| Predicate | hasDistinctLowercase |
P33607
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Pollard script, hasDistinctLowercase, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctLowercase Context triple: [Pollard script, hasDistinctLowercase, no]
-
A.
hasDistinctUppercase
Indicates that the related entity or string contains at least one uppercase character that is different from the others (i.e., not all uppercase characters are identical).
-
B.
hasDistinctUpperLowerCase
Indicates that the subject uses both uppercase and lowercase letter forms in a distinguishable way.
-
C.
hasDistinctLetters
Indicates that all letters in the given string or word are unique, with no character repeated.
-
D.
hasLowercaseLetters
chosen
Indicates that the referenced text contains at least one lowercase alphabetic character.
-
E.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 6:24 p.m.