Triple
T29120691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galaxy Science Fiction |
E737172
|
entity |
| Predicate | notableSerializedWork |
P24127
|
FINISHED |
| Object | The Demolished Man |
E598890
|
NE 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: The Demolished Man | Statement: [Galaxy Science Fiction, notableSerializedWork, The Demolished Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSerializedWork Context triple: [Galaxy Science Fiction, notableSerializedWork, The Demolished Man]
-
A.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
B.
notableWorkSeries
Indicates that a work is part of a series for which the subject is notably known or recognized.
-
C.
notableWorkContained
chosen
Indicates that a notable work is included within or is part of another entity, such as a collection, publication, or compilation.
-
D.
notableTypeOfWork
Indicates that a work is a significant or defining example within a particular type or category of work associated with an entity.
-
E.
notableWorkWrittenIn
Indicates that a notable work was written in a particular language, place, or time period.
- F. None of above.
Provenance (4 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02fc3890a881908b69b0f2d7cc1ce1 |
completed | May 12, 2026, 10:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2537ca9fd4819082b8559c2b00d38d |
completed | June 7, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_6a02fb98438c8190938896c00216b9ec |
completed | May 12, 2026, 10:06 a.m. |
Created at: April 28, 2026, 11:25 a.m.