Triple
T29365473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine Varangian Guard |
E744703
|
entity |
| Predicate | notableEthnicComponent |
P111672
|
FINISHED |
| Object | Norse |
—
|
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: Norse | Statement: [Byzantine Varangian Guard, notableEthnicComponent, Norse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEthnicComponent Context triple: [Byzantine Varangian Guard, notableEthnicComponent, Norse]
-
A.
ethnicComponents
chosen
Indicates that an entity is composed of, associated with, or characterized by one or more specified ethnic groups or ethnic origins.
-
B.
notableBearerEthnicity
Indicates that the notable person bearing something (such as a name, title, or role) belongs to a specified ethnic group.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
E.
ethnoGeneticRole
Indicates the role or function an entity has in the origin, formation, or transmission of an ethnic or genetic lineage.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0352b6c7dc81908f190060eb1e1857 |
completed | May 12, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_6a03507c37d4819091068b2ec5cacef9 |
completed | May 12, 2026, 4:08 p.m. |
Created at: April 28, 2026, 2:22 p.m.