Triple
T33457643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عبد السلام هارون (تحقيق وتعليق) |
E856820
|
entity |
| Predicate | يعتمد على |
P22819
|
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.
reliedOn
chosen
Indicates that one entity depends on another for support, resources, or functionality.
-
B.
basedOnRequirementOf
Indicates that something is established, created, or determined according to a specified requirement or set of requirements.
-
C.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
D.
dependency
Indicates that one entity relies on, is conditioned by, or cannot function or exist properly without another entity.
-
E.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4d0a7a8819090026ef0c5265f9e |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.