Triple
T10166321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eta |
E235211
|
entity |
| Predicate | hasLowercaseUsage |
P20861
|
FINISHED |
| Object | more common in scientific notation |
—
|
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: more common in scientific notation | Statement: [eta, hasLowercaseUsage, more common in scientific notation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowercaseUsage Context triple: [eta, hasLowercaseUsage, more common in scientific notation]
-
A.
hasLowercaseLetters
Indicates that the referenced text contains at least one lowercase alphabetic character.
-
B.
hasLowercaseForm
chosen
Indicates that one entity is the lowercase version or representation of another entity.
-
C.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
D.
hasUppercaseAndLowercase
Indicates that a string or text value contains at least one uppercase letter and at least one lowercase letter.
-
E.
hasLowercaseShapeDescription
Indicates that the entity’s shape is described using a string consisting only of lowercase characters.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6cf27481909f38839452ac0e37 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.