Triple
T30787799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kensiu language |
E784001
|
entity |
| Predicate | notTypicallyUsedInDomain |
P7974
|
FINISHED |
| Object | formal education |
—
|
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: formal education | Statement: [Kensiu language, notTypicallyUsedInDomain, formal education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notTypicallyUsedInDomain Context triple: [Kensiu language, notTypicallyUsedInDomain, formal education]
-
A.
notUsedInDomain
Indicates that a given element or resource is not utilized, referenced, or applicable within a specified domain or context.
-
B.
notTypicallyUsedFor
chosen
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
-
C.
usedInDomain
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
D.
notationDomain
Indicates a relationship where a notation system is associated with, or defined over, a particular domain in which it is valid or applicable.
-
E.
notTypically
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
- 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_69f6900ab06c8190856785240a8faa83 |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.