Triple
T2186314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sūrāyē |
E49159
|
entity |
| Predicate | ethnicIdentityLinkedTo |
P194
|
FINISHED |
| Object | ancient Assyrian heritage |
—
|
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: ancient Assyrian heritage | Statement: [Sūrāyē, ethnicIdentityLinkedTo, ancient Assyrian heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicIdentityLinkedTo Context triple: [Sūrāyē, ethnicIdentityLinkedTo, ancient Assyrian heritage]
-
A.
ethnoreligiousIdentity
Indicates a relationship where an entity is characterized by a combined ethnic and religious group identity.
-
B.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
C.
ethnicOrigin
chosen
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
D.
citizenshipLinkedTo
Indicates that there is an established connection between an entity and a specific citizenship status, such as holding, sharing, or being associated with that citizenship.
-
E.
ethnicCategoryIn
Indicates that an entity belongs to or is classified within a specified ethnic category in a given context.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.