Triple
T25345201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carache |
E635525
|
entity |
| Predicate | hasRegionalLanguageOfCountry |
P10892
|
FINISHED |
| Object | Crioulo |
—
|
NE NERFINISHED |
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: Crioulo | Statement: [Carache, hasRegionalLanguageOfCountry, Crioulo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalLanguageOfCountry Context triple: [Carache, hasRegionalLanguageOfCountry, Crioulo]
-
A.
hasLanguageInCountry
Indicates that a particular language is used or recognized within a specified country.
-
B.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
-
C.
hasLanguageOfSurroundingCountries
Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
-
D.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
E.
regionLanguage
chosen
Indicates that a particular language is used or officially recognized 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 21, 2026, 1:34 p.m.