Triple
T11408255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert |
E270293
|
entity |
| Predicate | isGivenNameInCulture |
P99146
|
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: [Albert, isGivenNameInCulture, English-speaking countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGivenNameInCulture Context triple: [Albert, isGivenNameInCulture, English-speaking countries]
-
A.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
B.
hasLatinizedName
Indicates that an entity is associated with a version of its name that has been converted into Latin form or spelling.
-
C.
hasNameInSlavonic
Indicates that an entity has a specific name or designation expressed in a Slavonic language.
-
D.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
E.
isIndigenousLanguageNameOf
Indicates that a given name is the name of a language as expressed in an indigenous language.
- F. None of above. chosen
Provenance (4 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_69d8014e72748190a01bde2f0105cedb |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.