Triple
T4759900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeta |
E105673
|
entity |
| Predicate | hasLowercaseShapeDescription |
P58353
|
FINISHED |
| Object | resembles a cursive or looped form with descender |
—
|
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: resembles a cursive or looped form with descender | Statement: [Zeta, hasLowercaseShapeDescription, resembles a cursive or looped form with descender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowercaseShapeDescription Context triple: [Zeta, hasLowercaseShapeDescription, resembles a cursive or looped form with descender]
-
A.
hasLowercaseForm
Indicates that one entity is the lowercase version or representation of another entity.
-
B.
hasLowercaseLetters
Indicates that the referenced text contains at least one lowercase alphabetic character.
-
C.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
D.
hasUppercaseForm
Indicates that one textual entity is the uppercase version or representation of another textual entity.
-
E.
hasUppercaseAndLowercase
Indicates that a string or text value contains at least one uppercase letter and at least one lowercase letter.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650dc7fc81909b483ef3c456ae0d |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.