Triple
T897559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha |
E19376
|
entity |
| Predicate | hasStrokeOrder |
P20863
|
FINISHED |
| Object | defined in Greek handwriting standards |
—
|
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: defined in Greek handwriting standards | Statement: [Alpha, hasStrokeOrder, defined in Greek handwriting standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrokeOrder Context triple: [Alpha, hasStrokeOrder, defined in Greek handwriting standards]
-
A.
hasHandwritingOf
Indicates that one entity’s handwriting style or written text is attributed to, or produced by, another entity.
-
B.
hasCursiveJoining
Indicates that one written character is connected to another through cursive-style joining.
-
C.
hasWritingDirection
Indicates the direction in which writing or text is read or written for a given script, language, or text system.
-
D.
hasSyllabary
Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
-
E.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad2550c88190a624eb5627d472ad |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9635608190a297e2067b8dcee2 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4a38ec8190915916d80299ab55 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.