Triple
T10791520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-ʿAbbās |
E254589
|
entity |
| Predicate | onomasticType |
P95503
|
FINISHED |
| Object | personal name |
—
|
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: personal name | Statement: [al-ʿAbbās, onomasticType, personal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onomasticType Context triple: [al-ʿAbbās, onomasticType, personal name]
-
A.
typeOfToponym
Indicates the specific category or kind of place name (toponym) that applies to a given geographic entity.
-
B.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
C.
commonInOnomastics
Indicates that a name, term, or pattern frequently appears or is widely used within the study and practice of naming (onomastics).
-
D.
hasDemonym
Indicates that one entity is the term (demonym) used to refer to the inhabitants or natives of another entity (typically a place).
-
E.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f6dfcc81909096895c588ef46f |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.