Triple
T38056621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quilmes (archaeological site) |
E950219
|
entity |
| Predicate | languageOfOriginalInhabitants |
P203729
|
FINISHED |
| Object | Cacán (extinct language) |
E950223
|
NE 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: Cacán (extinct language) | Statement: [Quilmes (archaeological site), languageOfOriginalInhabitants, Cacán (extinct language)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfOriginalInhabitants Context triple: [Quilmes (archaeological site), languageOfOriginalInhabitants, Cacán (extinct language)]
-
A.
languageOfColonialSettlers
Indicates the language historically spoken by colonial settlers in a given place or context.
-
B.
languageOfFounders
Indicates the language or languages spoken or used by the founders of an entity.
-
C.
languageOfAdoption
Indicates the language in which an adoption (e.g., of a text, standard, or practice) is formally made or recorded.
-
D.
isSpokenPrimarilyByTribalCommunities
Indicates that a language is used mainly as the primary means of communication by tribal or indigenous communities.
-
E.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
- F. None of above. chosen
Provenance (5 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01d339feac8190a3de56b24db67163 |
completed | May 11, 2026, 1:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d356f7881909dbdc4ee8fff1e58 |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a01d2bc1f408190a04869f95e6941ee |
completed | May 11, 2026, 12:59 p.m. |
| PDg | Predicate description generation | batch_6a01d3394e0481909ec86ddd283e76c5 |
completed | May 11, 2026, 1:01 p.m. |
Created at: May 3, 2026, 4:21 p.m.