Triple
T3920957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay Islands English |
E88955
|
entity |
| Predicate | hasContactSituation |
P12914
|
FINISHED |
| Object | intense contact with Spanish in the Bay Islands |
—
|
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: intense contact with Spanish in the Bay Islands | Statement: [Bay Islands English, hasContactSituation, intense contact with Spanish in the Bay Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactSituation Context triple: [Bay Islands English, hasContactSituation, intense contact with Spanish in the Bay Islands]
-
A.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for another entity.
-
B.
hasKontakion
Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
-
C.
hasContactType
chosen
Indicates the specific kind or category of contact relationship that exists between two entities.
-
D.
hasContactMethod
Indicates that an entity has a specific way or channel through which it can be contacted.
-
E.
historicalContactWith
Indicates that two entities have interacted or been in communication with each other at some point in the past.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.