Triple
T1990033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thaana script |
E43230
|
entity |
| Predicate | scriptFamilyInfluence |
P31348
|
FINISHED |
| Object | Arabic script |
—
|
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 script | Statement: [Thaana script, scriptFamilyInfluence, Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptFamilyInfluence Context triple: [Thaana script, scriptFamilyInfluence, Arabic script]
-
A.
scriptFamily
Indicates that one writing system belongs to the same broader script group or classification as another.
-
B.
macroFamily
Indicates that two or more language families are hypothesized to share a common higher-level genetic origin, forming a larger proposed macro-family grouping.
-
C.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
-
D.
typeOfInfluence
chosen
Indicates the specific nature or category of influence that one entity exerts on another.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.