Triple
T23387665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-7 |
E593926
|
entity |
| Predicate | doesNotFullySupport |
P148414
|
FINISHED |
| Object | polytonic Greek orthography |
—
|
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: polytonic Greek orthography | Statement: [ISO/IEC 8859-7, doesNotFullySupport, polytonic Greek orthography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotFullySupport Context triple: [ISO/IEC 8859-7, doesNotFullySupport, polytonic Greek orthography]
-
A.
doesNotFullySupportLanguage
chosen
Indicates that an entity provides only partial or limited support for a specified language, rather than full compatibility or functionality.
-
B.
doNotSupport
Indicates that one entity withholds help, approval, or endorsement from another entity or action.
-
C.
notSupportedBy
Indicates that an entity does not receive assistance, endorsement, or backing from another entity.
-
D.
partiallySupportedBy
Indicates that something receives incomplete, limited, or not fully sufficient support from another entity.
-
E.
notFullyAdoptedIn
Indicates that something has not been completely or universally implemented, accepted, or put into practice within a specified context or domain.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498fd08819085e90a872d9d0c7a |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.