Triple
T32924873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalál |
E842238
|
entity |
| Predicate | isNamedAccordingTo |
P175866
|
FINISHED |
| Object | Names of God |
—
|
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: Names of God | Statement: [Jalál, isNamedAccordingTo, Names of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedAccordingTo Context triple: [Jalál, isNamedAccordingTo, Names of God]
-
A.
isNamedEntity
Indicates that the subject is recognized as a named entity, such as a specific person, organization, location, or other proper noun.
-
B.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
C.
isNamedUnit
Indicates that an entity is a unit of measurement that has an explicit, conventional name rather than being expressed purely in derived or composite form.
-
D.
coNamedWith
Indicates that two or more entities share the same name or are designated by an identical label.
-
E.
isAcceptedName
Indicates that a given name is the currently recognized, valid, and officially accepted designation for an entity within a particular naming or classification system.
- F. None of above. chosen
Provenance (4 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:20 a.m.