Triple
T27870955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pollard script |
E704488
|
entity |
| Predicate | hasDistinctUppercase |
P185628
|
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, hasDistinctUppercase, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctUppercase Context triple: [Pollard script, hasDistinctUppercase, no]
-
A.
hasDistinctUpperLowerCase
Indicates that the subject uses both uppercase and lowercase letter forms in a distinguishable way.
-
B.
hasUppercase
Indicates that an entity contains at least one uppercase (capital) letter.
-
C.
hasDistinctLetters
Indicates that all letters in the given string or word are unique, with no character repeated.
-
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.
hasUppercaseUsage
Indicates that an entity is used or represented with uppercase letters in a particular context or form.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 27, 2026, 6:24 p.m.