Triple
T28411699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karimi |
E719679
|
entity |
| Predicate | hasFrequencyCategoryInIran |
P28499
|
FINISHED |
| Object | common surname |
—
|
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: common surname | Statement: [Karimi, hasFrequencyCategoryInIran, common surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrequencyCategoryInIran Context triple: [Karimi, hasFrequencyCategoryInIran, common surname]
-
A.
hasFrequencyCategory
chosen
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
B.
frequencyCategory
Indicates how often an action, event, or relationship occurs, typically by assigning it to a qualitative frequency level (e.g., rare, occasional, frequent).
-
C.
hasApproximateEuropeanFrequency
Indicates that the subject has an estimated or approximate occurrence rate within European populations.
-
D.
hasFrequencyChannels
Indicates that an entity is associated with, or operates over, one or more specific frequency channels.
-
E.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 1:27 a.m.