Triple
T24777318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | da Gama |
E619894
|
entity |
| Predicate | onLanguageList |
P157116
|
FINISHED |
| Object | list of Portuguese-language surnames |
—
|
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: list of Portuguese-language surnames | Statement: [da Gama, onLanguageList, list of Portuguese-language surnames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onLanguageList Context triple: [da Gama, onLanguageList, list of Portuguese-language surnames]
-
A.
languageCollection
Indicates a relationship where an entity maintains or is associated with a set or collection of languages.
-
B.
languageOfOfficialLists
Indicates the language in which official lists, records, or registries are formally maintained or published.
-
C.
navigationLanguage
Indicates the language used for navigation-related content, such as menus, directions, or interface controls.
-
D.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
E.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410d3ea308190ae80cb7d5bf94249 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:38 a.m.