Triple
T9460809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarikoli |
E228138
|
entity |
| Predicate | primaryDomainOfUse |
P1902
|
FINISHED |
| Object | home and local community |
—
|
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: home and local community | Statement: [Sarikoli, primaryDomainOfUse, home and local community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDomainOfUse Context triple: [Sarikoli, primaryDomainOfUse, home and local community]
-
A.
primaryDomain
chosen
Indicates that one domain is the main or most important domain associated with an entity, as opposed to any secondary or alternate domains.
-
B.
originalPrimaryUse
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
C.
regionPrimaryUse
Indicates the main functional purpose or dominant activity for which a region is used.
-
D.
primarilyUsedBy
Indicates that something is mainly or most commonly used by a particular entity or group.
-
E.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcaf610819092bcd3b871665aa5 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.