Triple
T31892319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 639-3 |
E814176
|
entity |
| Predicate | includesDialects |
P4251
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [ISO 639-3, includesDialects, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDialects Context triple: [ISO 639-3, includesDialects, no]
-
A.
hasDialects
chosen
Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
-
B.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
-
C.
implementsDialectOf
Indicates that one entity realizes or carries out a specific dialect, variant, or localized form of another entity (such as a language, standard, or protocol).
-
D.
usesDialect
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
-
E.
hasParticularDialect
Indicates that an entity uses, is associated with, or is characterized by a specific dialect of a language.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a018f9c7cf88190adc5daf3806f2077 |
completed | May 11, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_6a018ca4e0e481908091f0c1f8a4c31b |
completed | May 11, 2026, 8 a.m. |
Created at: April 30, 2026, 11:58 p.m.