Triple
T29732356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marc C. DuQuesne |
E752363
|
entity |
| Predicate | isFromWorkSetIn |
P122616
|
FINISHED |
| Object | interstellar setting |
—
|
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: interstellar setting | Statement: [Marc C. DuQuesne, isFromWorkSetIn, interstellar setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromWorkSetIn Context triple: [Marc C. DuQuesne, isFromWorkSetIn, interstellar setting]
-
A.
usedInWorkSetIn
Indicates that something (such as an element, motif, or device) is employed within a creative work whose narrative or content is set in a particular place or time.
-
B.
appearsInWorkSetIn
Indicates that an entity appears in a creative work whose narrative or setting takes place in a specified location or context.
-
C.
isFromWorkCreatedIn
chosen
Indicates that something originates from or is derived from a work that was created in a specific context, such as a place, time, or setting.
-
D.
workInSet
Indicates that an entity performs work or has a role within a specified set, group, or collection.
-
E.
hasWorkInCollection
Indicates that a work or item is included as part of a particular collection.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67331be608190b98b26bddb4e69b7 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:43 p.m.