Triple
T3920958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay Islands English |
E88955
|
entity |
| Predicate | hasDomainOfUse |
P5018
|
FINISHED |
| Object | informal communication |
—
|
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: informal communication | Statement: [Bay Islands English, hasDomainOfUse, informal communication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomainOfUse Context triple: [Bay Islands English, hasDomainOfUse, informal communication]
-
A.
usedInDomain
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
B.
scopeOfUse
chosen
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
C.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
D.
hasTypicalUsageRegion
Indicates that something is most commonly or characteristically used within a particular geographic region.
-
E.
hasLegalDomain
Indicates that a legal rule, right, obligation, or concept applies within a specific jurisdiction, legal system, or domain of law.
- 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.