Triple
T30787686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batek language |
E783998
|
entity |
| Predicate | hasRegisterContrast |
P50776
|
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: [Batek language, hasRegisterContrast, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegisterContrast Context triple: [Batek language, hasRegisterContrast, no]
-
A.
registerContrast
chosen
Indicates that an entity records or establishes a distinction or difference between two or more items or states.
-
B.
hasContrastType
Indicates that one entity is associated with a specific type or category of contrast used to distinguish it from others.
-
C.
hasDensityContrast
Indicates that one entity differs from another in material density, highlighting a contrast in how compact or dense they are.
-
D.
includesContrast
Indicates that one element contains or incorporates a comparison highlighting differences between two or more entities or ideas.
-
E.
hasMainContrast
Indicates a primary opposing or differing relationship between two elements, highlighting the main point of contrast between them.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00b03a50a88190bfb95cdcfc6142a2 |
completed | May 10, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_6a00afe55f248190b2cb4c7e62cc3ffc |
completed | May 10, 2026, 4:18 p.m. |
Created at: April 29, 2026, 8:41 p.m.