Triple
T8724511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlapanecan languages |
E207096
|
entity |
| Predicate | haveTypology |
P5753
|
FINISHED |
| Object | tonal 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: tonal languages | Statement: [Tlapanecan languages, haveTypology, tonal languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveTypology Context triple: [Tlapanecan languages, haveTypology, tonal languages]
-
A.
typology
chosen
Indicates a classification relationship in which entities are grouped or organized according to shared types, patterns, or structural characteristics.
-
B.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
theoryType
Indicates the classification relationship that specifies what type or category of theory an entity belongs to.
-
E.
hasStratotype
Indicates that one entity serves as the designated standard or reference example (stratotype) for defining the stratigraphic characteristics of another entity.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d1404948190bc45d14a1ddb1a7e |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.