Triple
T31595366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eparchy of Lungro |
E806203
|
entity |
| Predicate | hasFaithfulOfEthnicity |
P123087
|
FINISHED |
| Object | Arbëreshë |
—
|
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: Arbëreshë | Statement: [Eparchy of Lungro, hasFaithfulOfEthnicity, Arbëreshë]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaithfulOfEthnicity Context triple: [Eparchy of Lungro, hasFaithfulOfEthnicity, Arbëreshë]
-
A.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
B.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
C.
supportedByEthnicGroup
Indicates that an entity receives backing, endorsement, or assistance from a particular ethnic group.
-
D.
hasEthnoreligiousRole
Indicates that an entity holds a role, function, or status defined by a combined ethnic and religious identity within a given context.
-
E.
hasEthnicScope
chosen
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 30, 2026, 10:30 p.m.