Triple
T16601592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Verdean people |
E403341
|
entity |
| Predicate | languageFamilyOfCreole |
P35117
|
FINISHED |
| Object | Portuguese‑based Creole |
—
|
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: Portuguese‑based Creole | Statement: [Cape Verdean people, languageFamilyOfCreole, Portuguese‑based Creole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyOfCreole Context triple: [Cape Verdean people, languageFamilyOfCreole, Portuguese‑based Creole]
-
A.
languageFamilyOfMajorCreole
Indicates that a given language family is the primary source or base language group from which a particular major creole language is derived.
-
B.
hasCreoleLanguage
Indicates that an entity possesses, uses, or is associated with a creole language.
-
C.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
D.
languageFamilyOf
chosen
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
E.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d764574819081366374ca0c9bea |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.