Triple
T5283518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasak |
E119554
|
entity |
| Predicate | historicalScriptUse |
P4037
|
FINISHED |
| Object | Arabic-based script for religious texts |
—
|
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: Arabic-based script for religious texts | Statement: [Sasak, historicalScriptUse, Arabic-based script for religious texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalScriptUse Context triple: [Sasak, historicalScriptUse, Arabic-based script for religious texts]
-
A.
historicalScript
chosen
Indicates that an entity is or was written in, or otherwise associated with, a particular historical writing system or script.
-
B.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
C.
historicalLanguageFeature
Indicates that a language possesses a feature, trait, or characteristic that existed or was relevant in a past historical period.
-
D.
hasHistoriographicalUse
Indicates that something is used or cited within historical writing or analysis as part of constructing, interpreting, or debating historical narratives.
-
E.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.