Triple
T22300884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wajo dialect |
E551250
|
entity |
| Predicate | ISO639-3CodeOfParentLanguage |
P36930
|
FINISHED |
| Object | bug |
—
|
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: bug | Statement: [Wajo dialect, ISO639-3CodeOfParentLanguage, bug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639-3CodeOfParentLanguage Context triple: [Wajo dialect, ISO639-3CodeOfParentLanguage, bug]
-
A.
sharesISO639-3CodeWith
Indicates that two language entities share the same ISO 639-3 code, meaning they are treated as the same language in that coding system.
-
B.
ISO639-3CodeOfLanguage
chosen
Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other entity.
-
C.
ISO639-3ReferenceName
Indicates the standardized reference name assigned to a language in the ISO 639-3 coding system.
-
D.
ISO639-6Code
Indicates the standardized ISO 639-6 four-letter code that uniquely identifies a specific language variety or dialect.
-
E.
ISO639Macrolanguage
Indicates that a language variety is part of a broader ISO 639-defined macrolanguage grouping that encompasses multiple closely related individual languages.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1572399148190853c4e91fcf9f38c |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.