Triple
T11424247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moru–Madi languages |
E270703
|
entity |
| Predicate | areRelatedBy |
P37
|
FINISHED |
| Object | shared phonological features |
—
|
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: shared phonological features | Statement: [Moru–Madi languages, areRelatedBy, shared phonological features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areRelatedBy Context triple: [Moru–Madi languages, areRelatedBy, shared phonological features]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
C.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
-
D.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
E.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806be9c2c819084da13101cbb6c81 |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.