Triple
T12155768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adlam script |
E289569
|
entity |
| Predicate | designedForOrthographicReform |
P89659
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Adlam script, designedForOrthographicReform, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForOrthographicReform Context triple: [Adlam script, designedForOrthographicReform, true]
-
A.
hasOrthographicReform
Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
-
B.
orthographicIndependence
Indicates that one writing system or orthographic form functions independently of, and is not derived from or constrained by, another.
-
C.
orthographicVariant
Indicates that two written forms are different spellings or orthographic representations of the same linguistic item.
-
D.
hasOrthographyProposal
chosen
Indicates that an entity is associated with a proposed system or set of rules for its written form or spelling.
-
E.
hasOrthographicConvention
Indicates that there is a specific writing or spelling convention that governs how something is represented in written form.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.