Triple
T32583964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santo Domingo del Estado Trique |
E832868
|
entity |
| Predicate | isVarietyOfISO639-3 |
P170714
|
FINISHED |
| Object | trc |
—
|
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: trc | Statement: [Santo Domingo del Estado Trique, isVarietyOfISO639-3, trc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVarietyOfISO639-3 Context triple: [Santo Domingo del Estado Trique, isVarietyOfISO639-3, trc]
-
A.
isVarietyOfISO6393
chosen
Indicates that one language variety is classified under, or corresponds to, a specific ISO 639-3 language code.
-
B.
ISO639-3Type
Indicates the classification type assigned to a language within the ISO 639-3 standard (e.g., living, extinct, ancient, constructed, or special).
-
C.
hasISO6393Code
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
-
D.
haveISO639Code
Indicates that a language or linguistic entity is associated with a specific ISO 639 standardized language code.
-
E.
ISO639-3CodeOfLanguage
Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c66c41b481908abc65d5d284bcee |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.