Triple
T26296956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBR |
E661442
|
entity |
| Predicate | commonUseContext |
P91215
|
FINISHED |
| Object | scanned comic books |
—
|
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: scanned comic books | Statement: [CBR, commonUseContext, scanned comic books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonUseContext Context triple: [CBR, commonUseContext, scanned comic books]
-
A.
originalUseContext
Indicates the original situation, setting, or context in which something was intended to be used or applied.
-
B.
modernUsageContext
Indicates the contemporary or current context in which something is used, applied, or functions.
-
C.
commonUseCategory
Indicates that multiple entities share the same general category of use or functional purpose.
-
D.
contextType
chosen
Indicates the type or category of contextual information associated with an entity or event.
-
E.
communityUsage
Indicates how something is used, adopted, or engaged with by a particular community or group of people.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 26, 2026, 10:13 p.m.