Triple
T22498074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rum millet |
E556195
|
entity |
| Predicate | notDefinedPrimarilyBy |
P148443
|
FINISHED |
| Object | ethnicity |
—
|
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: ethnicity | Statement: [Rum millet, notDefinedPrimarilyBy, ethnicity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notDefinedPrimarilyBy Context triple: [Rum millet, notDefinedPrimarilyBy, ethnicity]
-
A.
doesNotPrimarilyContain
Indicates that one entity does not have another entity as its main or predominant component, element, or content.
-
B.
notPrimarilyIntendedFor
Indicates that something is used or occurs in a way that is not its main or original purpose or target.
-
C.
doesNotPrimarilyAddress
Indicates that something fails to mainly focus on, deal with, or concern a particular topic, issue, or entity.
-
D.
doesNotPrimarilyProvide
Indicates that one entity does not mainly or chiefly supply, offer, or furnish a particular service, resource, or function to another entity.
-
E.
doesNotPrimarilyUse
Indicates that the subject entity does not mainly or predominantly employ, rely on, or make use of the specified object or method.
- F. None of above. chosen
Provenance (4 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb31b8081909553fa860a07e746 |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:50 p.m.