Triple
T30162364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords of Ainos |
E766700
|
entity |
| Predicate | ethnicallyLinkedTo |
P1969
|
FINISHED |
| Object | Genoese nobility |
—
|
NE NERFINISHED |
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: Genoese nobility | Statement: [Lords of Ainos, ethnicallyLinkedTo, Genoese nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicallyLinkedTo Context triple: [Lords of Ainos, ethnicallyLinkedTo, Genoese nobility]
-
A.
relatedEthnicGroup
chosen
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
B.
relatedEthnonymNote
Indicates that there is an explanatory note describing how this ethnonym is related to another ethnonym or term.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
isEthnonymFor
Indicates that one term is the ethnonym (name of a people or ethnic group) used to refer to another entity.
-
E.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 7:22 p.m.