Triple
T25680815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tariano |
E643933
|
entity |
| Predicate | hasNeighborLanguageContact |
P95982
|
FINISHED |
| Object | Tucano |
—
|
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: Tucano | Statement: [Tariano, hasNeighborLanguageContact, Tucano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighborLanguageContact Context triple: [Tariano, hasNeighborLanguageContact, Tucano]
-
A.
hasNeighboringLanguages
Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
-
B.
hasContactWithLanguage
chosen
Indicates that an entity has some form of interaction, exposure, or engagement with a particular language.
-
C.
hasNeighboringLanguageCommunity
Indicates that one language community is geographically or socially adjacent to another, allowing for direct contact or interaction between them.
-
D.
hasDominantNeighborLanguage
Indicates that an entity’s primary neighboring language exerts a dominant influence or holds a superior status over other nearby languages.
-
E.
hasLanguageOfSurroundingCountries
Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 21, 2026, 7:58 p.m.