Triple
T6638068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subanen languages |
E150507
|
entity |
| Predicate | geneticallyRelatedTo |
P27906
|
FINISHED |
| Object | other Greater Central Philippine 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 Greater Central Philippine languages | Statement: [Subanen languages, geneticallyRelatedTo, other Greater Central Philippine languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticallyRelatedTo Context triple: [Subanen languages, geneticallyRelatedTo, other Greater Central Philippine languages]
-
A.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
B.
notGeneticallyRelatedTo
Indicates that there is no genetic or hereditary relationship between the two entities.
-
C.
geneticAffinity
chosen
Indicates a relationship where entities share a notable degree of genetic similarity or relatedness.
-
D.
relatedSpeciesOrVariant
Indicates that one species or biological variant is taxonomically or genetically related to another.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 2 p.m.