Triple
T11413413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salentino dialect |
E270427
|
entity |
| Predicate | hasHistoricalContact |
P4255
|
FINISHED |
| Object | Byzantine Greek communities in Apulia |
—
|
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: Byzantine Greek communities in Apulia | Statement: [Salentino dialect, hasHistoricalContact, Byzantine Greek communities in Apulia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalContact Context triple: [Salentino dialect, hasHistoricalContact, Byzantine Greek communities in Apulia]
-
A.
historicalContactWith
chosen
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
B.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
C.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
D.
hasHistoryNote
Indicates that there is an associated historical note or record describing past events, changes, or context related to the subject.
-
E.
hasAccessRestrictionHistory
Indicates that there exists a record or sequence of past changes detailing how access to something has been restricted over time.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801acd9bc81908a23b1b7b4e778d3 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.