Triple
T20005902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krys Marshall |
E494459
|
entity |
| Predicate | hasNotableThemeInWork |
P494
|
FINISHED |
| Object | space exploration |
—
|
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: space exploration | Statement: [Krys Marshall, hasNotableThemeInWork, space exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableThemeInWork Context triple: [Krys Marshall, hasNotableThemeInWork, space exploration]
-
A.
hasNotableWorkSetThere
Indicates that a notable work (such as a book, film, or other creative piece) is set in or takes place within the referenced location.
-
B.
hasNotableSubject
chosen
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
C.
hasNotableWorkCategory
Indicates that an entity’s notable work belongs to, or is classified under, a particular category or type.
-
D.
hasNotableWorkExample
Indicates that an entity has a specific notable work cited as an example associated with it.
-
E.
hasNotableWorkRights
Indicates that an entity holds legal or recognized rights associated with a notable work, such as authorship, ownership, or usage rights.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a57ef881909115c8aa232b1012 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.