Triple
T24907141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ʿĀd |
E623737
|
entity |
| Predicate | calledInArabicScript |
P125165
|
FINISHED |
| Object | عاد |
—
|
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: عاد | Statement: [ʿĀd, calledInArabicScript, عاد]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calledInArabicScript Context triple: [ʿĀd, calledInArabicScript, عاد]
-
A.
hasNameInArabic
Indicates that an entity is associated with a specific name expressed in the Arabic language.
-
B.
hasGivenNameFormInArabic
Indicates that an entity has a specific given-name form expressed in the Arabic language.
-
C.
correspondsToInArabic
chosen
Indicates that one entity is the equivalent or matching counterpart of another entity specifically in the Arabic language.
-
D.
endsWithArabic
Indicates that one entity’s content or representation terminates with Arabic script or characters.
-
E.
hasOpeningWordsArabic
Indicates that an entity (such as a text, document, or work) has specific opening words expressed in the Arabic language.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4236bc540819096275eb784a08719 |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:27 a.m.