Triple
T36406161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabic root R-Š-D (رشَد) |
E896753
|
entity |
| Predicate | verbalNounPattern |
P5220
|
FINISHED |
| Object | fuʿl (رُشْد) |
—
|
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: fuʿl (رُشْد) | Statement: [Arabic root R-Š-D (رشَد), verbalNounPattern, fuʿl (رُشْد)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verbalNounPattern Context triple: [Arabic root R-Š-D (رشَد), verbalNounPattern, fuʿl (رُشْد)]
-
A.
hasVerbalMorphology
Indicates that one linguistic element exhibits verbal inflectional properties or patterns in relation to another.
-
B.
hasVerbalSuffixes
Indicates that a language, word, or grammatical form possesses specific suffixes that are attached to verbs.
-
C.
hasVerbalFeature
Indicates that an entity possesses a specific verbal property, characteristic, or behavior related to speech or language.
-
D.
hasNounEnding
chosen
Indicates that something possesses or exhibits a particular noun-forming ending or suffix.
-
E.
hasVerbFinalTendency
Indicates that an entity (such as a language or construction) tends to place the main verb at or near the end of the clause or sentence.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.