Triple
T32075031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ixcateco |
E819119
|
entity |
| Predicate | isUsedPrimarilyIn |
P10000
|
FINISHED |
| Object | domestic domains |
—
|
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: domestic domains | Statement: [Ixcateco, isUsedPrimarilyIn, domestic domains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedPrimarilyIn Context triple: [Ixcateco, isUsedPrimarilyIn, domestic domains]
-
A.
isPrimarilyUsedAs
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
B.
usedPrimarilyIn
chosen
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
C.
performsPrimarilyIn
Indicates that an entity (such as a performer or group) mainly carries out its performances within a particular location, medium, or context.
-
D.
primarilyUsedBy
Indicates that something is mainly or most commonly used by a particular entity or group.
-
E.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:23 a.m.