Triple
T6472832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laiyolo–Kaili languages |
E145995
|
entity |
| Predicate | sharesCommonAncestryWith |
P18399
|
FINISHED |
| Object | other Celebic languages |
—
|
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: other Celebic languages | Statement: [Laiyolo–Kaili languages, sharesCommonAncestryWith, other Celebic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCommonAncestryWith Context triple: [Laiyolo–Kaili languages, sharesCommonAncestryWith, other Celebic languages]
-
A.
sharesCommonAncestorWith
chosen
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
-
B.
sharesComplexWith
Indicates that two entities are components of, or co-residents within, the same larger complex or composite structure.
-
C.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
-
D.
hasLastNameInCommonWith
Indicates that two entities share the same last name.
-
E.
sharesHistoryWith
Indicates that two entities have a common or overlapping past, such as shared experiences, events, or origins.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a3188488190a1b7452ede91ba5e |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:50 p.m.