Triple
T34947326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupi language |
E1007889
|
entity |
| Predicate | notableLoanwordToPortuguese |
P206748
|
FINISHED |
| Object | abacaxi |
—
|
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: abacaxi | Statement: [Tupi language, notableLoanwordToPortuguese, abacaxi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLoanwordToPortuguese Context triple: [Tupi language, notableLoanwordToPortuguese, abacaxi]
-
A.
cognateInPortuguese
Indicates that a word or term has a cognate (a related form with common etymological origin) in Portuguese.
-
B.
hasPortugueseNameMeaning
Indicates that an entity has a Portuguese name whose semantic meaning is being specified or referenced.
-
C.
hasAbbreviationInPortuguese
Indicates that one entity is used as the Portuguese-language abbreviation or shortened form of another entity.
-
D.
nameInPortuguese
Indicates that an entity is referred to by a specific name when expressed in the Portuguese language.
-
E.
IPAInBrazilianPortuguese
Indicates that something represents or is expressed using the International Phonetic Alphabet (IPA) as used for Brazilian Portuguese pronunciation.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4 p.m.