Triple
T1312315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linda |
E28018
|
entity |
| Predicate | becamePopularInRegion |
P9666
|
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: [Linda, becamePopularInRegion, English-speaking countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becamePopularInRegion Context triple: [Linda, becamePopularInRegion, English-speaking countries]
-
A.
primaryRegionOfPopularity
chosen
Indicates the geographic region where something is most widely used, favored, or popular compared to other regions.
-
B.
emergedInRegion
Indicates that something first appeared, originated, or came into existence within a specified geographic region.
-
C.
developedInRegion
Indicates that something was created, produced, or brought into existence within a specified geographic region.
-
D.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
regionallyKnownAs
Indicates that an entity is known by a particular name or designation within a specific geographic region.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1572b1c8190ab978198c2d655c8 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.