Triple
T7081732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulawesi languages |
E164970
|
entity |
| Predicate | coexistWith |
P41297
|
FINISHED |
| Object | Indonesian language |
—
|
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: Indonesian language | Statement: [Sulawesi languages, coexistWith, Indonesian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coexistWith Context triple: [Sulawesi languages, coexistWith, Indonesian language]
-
A.
canCoexistWith
Indicates that two entities are able to exist together in the same context or environment without conflict, interference, or mutual exclusion.
-
B.
coexistsWithLanguage
chosen
Indicates that one entity exists or functions alongside a particular language at the same time, without excluding or replacing it.
-
C.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
D.
coexistedWith
Indicates that two entities existed at the same time and in the same context or environment, without implying any specific type of interaction between them.
-
E.
collocatedWith
Indicates that two entities are located in the same place or spatial context at the same time.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4f1f5748190b214856bcfc70d81 |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.