Triple
T31892318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 639-3 |
E814176
|
entity |
| Predicate | includesMacrolanguages |
P203476
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ISO 639-3, includesMacrolanguages, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMacrolanguages Context triple: [ISO 639-3, includesMacrolanguages, yes]
-
A.
hasMacrolanguage
Indicates that a language is part of, or grouped under, a broader macrolanguage that encompasses multiple closely related language varieties.
-
B.
macrolanguageWith
Indicates that one language is classified as a macrolanguage that encompasses or groups together another, more specific language variety.
-
C.
macrolanguage
Indicates that a language is classified as a macrolanguage encompassing multiple closely related individual languages or varieties.
-
D.
macrolanguageMemberOf
Indicates that a language variety is classified as a member of a larger macrolanguage grouping.
-
E.
macrolanguageOf
Indicates that one language functions as a macrolanguage encompassing or grouping together one or more related individual languages.
- F. None of above. chosen
Provenance (4 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a018c6b7178819097d5450a1e3c2408 |
completed | May 11, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_6a018a4f741c8190babe721a908e2f5e |
completed | May 11, 2026, 7:50 a.m. |
| PDg | Predicate description generation | batch_6a018c6aaca081908c63d8d624fe9ec4 |
completed | May 11, 2026, 7:59 a.m. |
Created at: April 30, 2026, 11:58 p.m.