Triple
T32303961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carapebus |
E825307
|
entity |
| Predicate | languageUsedInOfficialActs |
P236
|
FINISHED |
| Object | Portuguese |
—
|
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 | Statement: [Carapebus, languageUsedInOfficialActs, Portuguese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInOfficialActs Context triple: [Carapebus, languageUsedInOfficialActs, Portuguese]
-
A.
languageOfOfficialDuties
Indicates the language that a person or role is required or authorized to use when performing their official duties.
-
B.
languageOfOfficialReports
Indicates the language in which an entity’s official reports are written or issued.
-
C.
officialLanguage
chosen
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
D.
declaresOfficialLanguageOf
Indicates that an authority formally designates a particular language as the official language of a specified entity or jurisdiction.
-
E.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
Created at: May 1, 2026, 12:45 a.m.