Triple
T24069371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Every Building on the Sunset Strip |
E596181
|
entity |
| Predicate | originalPrintRun |
P3998
|
FINISHED |
| Object | 1000 copies |
—
|
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: 1000 copies | Statement: [Every Building on the Sunset Strip, originalPrintRun, 1000 copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPrintRun Context triple: [Every Building on the Sunset Strip, originalPrintRun, 1000 copies]
-
A.
printRun
Indicates the number or instance of times a particular item or edition has been printed or produced.
-
B.
firstEditionPrintRun
chosen
Indicates the initial quantity of copies produced when a work is printed in its first published edition.
-
C.
originalRunType
Indicates the initial or primary category or mode under which a particular run, execution, or process was originally conducted.
-
D.
printedFor
Indicates that one entity produced a printed version of something specifically intended for another entity as the recipient or audience.
-
E.
printedBy
Indicates that one entity is produced or output in physical or digital form by another entity acting as the printer or printing agent.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db15866c8190ab931216b8d9c57f |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.