Triple
T38125092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donnie |
E952044
|
entity |
| Predicate | typicalLanguageCommunity |
P5562
|
FINISHED |
| Object | English-speaking countries |
—
|
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: English-speaking countries | Statement: [Donnie, typicalLanguageCommunity, English-speaking countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLanguageCommunity Context triple: [Donnie, typicalLanguageCommunity, English-speaking countries]
-
A.
typicalLanguages
Indicates the languages that are commonly or characteristically used, spoken, or associated with a given entity.
-
B.
hasLanguageCommunity
chosen
Indicates that an entity is associated with or serves a particular language community.
-
C.
laterLanguageOfCommunity
Indicates that one language developed later in time as the language used by a particular community, succeeding an earlier community language.
-
D.
formerLanguageCommunity
Indicates that a group or community previously used a particular language but no longer does so.
-
E.
majorLanguageGroupOf
Indicates that one language group is the primary or dominant linguistic classification to which another language or set of languages belongs.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.