Triple
T7261271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aru languages |
E159656
|
entity |
| Predicate | contactLanguages |
P8345
|
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: [Aru languages, contactLanguages, Indonesian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contactLanguages Context triple: [Aru languages, contactLanguages, Indonesian language]
-
A.
contactLanguageWith
Indicates that two entities communicate with each other using a particular language as the medium of contact.
-
B.
primaryLanguageContact
Indicates that one language serves as the main or dominant medium of communication in a particular contact situation between language communities.
-
C.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
D.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
E.
usedAsContactLanguageBetween
chosen
Indicates that a language functions as the medium of communication between two or more distinct language communities.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.