Triple
T18317929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab Reading Challenge |
E438794
|
entity |
| Predicate | typeOfLiteracy |
P131318
|
FINISHED |
| Object | reading literacy |
—
|
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: reading literacy | Statement: [Arab Reading Challenge, typeOfLiteracy, reading literacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLiteracy Context triple: [Arab Reading Challenge, typeOfLiteracy, reading literacy]
-
A.
literacyStatus
Indicates whether an entity possesses the ability to read and write, or its level of literacy.
-
B.
literacyTestRequirement
Indicates that an entity is subject to, or must satisfy, a literacy test as a condition for participation in a specified activity or obtaining a particular status.
-
C.
literatureType
Indicates the specific category or genre of literature that characterizes or classifies a given work or text.
-
D.
hasLiteracyConcern
Indicates that an entity has an identified issue, risk, or challenge related to literacy skills or abilities.
-
E.
literacyRequirementAdministeredBy
Indicates that the administration or enforcement of a literacy requirement is carried out by a specified agent or authority.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021f5f1081909fd98c8fb786c7ff |
completed | April 19, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.