Triple
T36001729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | العرش |
E1041149
|
entity |
| Predicate | يفسره_بعض_المتكلمين |
P70128
|
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: [العرش, يفسره_بعض_المتكلمين, رمزاً للملك والسلطان]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يفسره_بعض_المتكلمين Context triple: [العرش, يفسره_بعض_المتكلمين, رمزاً للملك والسلطان]
-
A.
نوع_التفسير
Indicates the specific type or category of interpretation being applied to something.
-
B.
له_شروح
Indicates that something (typically a text, concept, or work) has one or more explanations or commentaries associated with it.
-
C.
misinterpretedBy
Indicates that something (such as a statement, action, or signal) is understood incorrectly or in a way not intended by a particular entity.
-
D.
interpretedInCase
Indicates that something is understood, analyzed, or given meaning within the context of a particular case or specific situational scenario.
-
E.
areInterpretedInPracticeBy
chosen
Indicates that something (such as a rule, concept, or specification) is given concrete meaning or applied in real-world situations by a particular agent or group.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.