Triple
T35202066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saraceni |
E1016433
|
entity |
| Predicate | relatedToEthnonym |
P150489
|
FINISHED |
| Object | Saracen |
E1220083
|
NE 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: Saracen | Statement: [Saraceni, relatedToEthnonym, Saracen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToEthnonym Context triple: [Saraceni, relatedToEthnonym, Saracen]
-
A.
relatedEthnonymNote
chosen
Indicates that there is an explanatory note describing how this ethnonym is related to another ethnonym or term.
-
B.
relatedEthnonymLanguageContext
Indicates that an ethnonym is associated with or derived from a particular language or linguistic context.
-
C.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
D.
associatedEthnicTerritories
Indicates that there is a relationship linking an entity to the ethnic territories with which it is historically, culturally, or demographically connected.
-
E.
linkedToEthnicIdentity
Indicates a relationship where something is associated or connected with a particular ethnic identity.
- F. None of above.
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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37fb2ba9088190a6048492be2ac82a |
completed | June 21, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.