Triple
T26106938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ar-Rahman |
E658560
|
entity |
| Predicate | requiresFormForHumanName |
P76927
|
FINISHED |
| Object | ʿAbd ar-Rahman |
—
|
NE NERFINISHED |
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: ʿAbd ar-Rahman | Statement: [Ar-Rahman, requiresFormForHumanName, ʿAbd ar-Rahman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresFormForHumanName Context triple: [Ar-Rahman, requiresFormForHumanName, ʿAbd ar-Rahman]
-
A.
usesNameForm
Indicates that one entity adopts or applies a particular standardized form or variant of a name associated with another entity.
-
B.
hasHumanFormName
Indicates that an entity’s human form is known by a specific name.
-
C.
requiresHumanResponse
Indicates that an action, event, or message necessitates a direct response or intervention from a human rather than being handled automatically.
-
D.
nativeForm
Indicates that one entity is the original or native linguistic form of another, such as a word’s form in its source language.
-
E.
nameRequirement
chosen
Indicates that there is a specified condition or constraint that a name must satisfy.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 26, 2026, 7:59 p.m.