Triple
T1800136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opus 100 |
E39697
|
entity |
| Predicate | includesWorkType |
P10663
|
FINISHED |
| Object | science fiction excerpts |
—
|
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: science fiction excerpts | Statement: [Opus 100, includesWorkType, science fiction excerpts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesWorkType Context triple: [Opus 100, includesWorkType, science fiction excerpts]
-
A.
workIncludes
chosen
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
B.
hasWorkforceType
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
C.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
D.
eligibleWorks
Indicates that certain works meet the required criteria or conditions to qualify for a specified status, use, or consideration.
-
E.
eligibleWork
Indicates that a particular work satisfies the necessary conditions or criteria to qualify for a specified status, benefit, or consideration.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.