Triple
T20348189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I. Somewhere Now (reprise) |
E495928
|
entity |
| Predicate | hasPartOfWorkNumber |
P95131
|
FINISHED |
| Object | I |
—
|
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: I | Statement: [I. Somewhere Now (reprise), hasPartOfWorkNumber, I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartOfWorkNumber Context triple: [I. Somewhere Now (reprise), hasPartOfWorkNumber, I]
-
A.
hasPartNumber
Indicates that one entity is assigned or associated with a specific part number used to identify it within a catalog, system, or inventory.
-
B.
hasNumberOfPartsInWholeWork
Indicates that an entity specifies how many component parts are contained within a complete work.
-
C.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
D.
hasWorkPart
chosen
Indicates that one work is a component, section, or constituent part of another, larger work.
-
E.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6783af5dc8190a40c3b9816cd1aef |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.