Triple
T37549753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turvali |
E933558
|
entity |
| Predicate | refersToMacroFamily |
P89917
|
FINISHED |
| Object | Indo-European languages |
—
|
NE NERFINISHED |
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: Indo-European languages | Statement: [Turvali, refersToMacroFamily, Indo-European languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToMacroFamily Context triple: [Turvali, refersToMacroFamily, Indo-European languages]
-
A.
belongsToMacrofamily
chosen
Indicates that a language is classified as part of a larger proposed language macrofamily.
-
B.
hasProposedMacroFamily
Indicates that one linguistic entity has been proposed as belonging to the same larger, hypothetical macro-family as another linguistic entity.
-
C.
macroFamily
Indicates that two or more language families are hypothesized to share a common higher-level genetic origin, forming a larger proposed macro-family grouping.
-
D.
belongsToFrameworkFamily
Indicates that one framework is a member of, or categorized under, a broader framework family or grouping.
-
E.
hasRepresentativeFamily
Indicates that an entity is associated with a particular family that serves as its representative or characteristic example.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 3, 2026, 4:17 p.m.