Triple
T29261745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Burnusi |
E741862
|
entity |
| Predicate | partOfNameType |
P5298
|
FINISHED |
| Object | nisba |
—
|
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: nisba | Statement: [al-Burnusi, partOfNameType, nisba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfNameType Context triple: [al-Burnusi, partOfNameType, nisba]
-
A.
partOfName
chosen
Indicates that one string is a component or substring that forms part of another entity’s name.
-
B.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
C.
partOfAppellation
Indicates that one name, title, or designation forms a component or subset of a larger, complete appellation.
-
D.
namesakeType
Indicates the specific kind or category of namesake relationship that exists between two entities (for example, one being named after the other as a person, place, event, or object).
-
E.
namedPartyType
Indicates the specific role or category that a referenced party holds within a given context or relationship.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: April 28, 2026, 12:42 p.m.