Triple
T29580926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estate of Isaac Asimov |
E753578
|
entity |
| Predicate | fieldOfWorkManaged |
P3
|
FINISHED |
| Object | science fiction literature |
—
|
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: science fiction literature | Statement: [Estate of Isaac Asimov, fieldOfWorkManaged, science fiction literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfWorkManaged Context triple: [Estate of Isaac Asimov, fieldOfWorkManaged, science fiction literature]
-
A.
fieldOfWork
chosen
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
B.
sectorManaged
Indicates that one entity is responsible for administering, overseeing, or directing the operations of a particular sector.
-
C.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
D.
genreOfWorkManaged
Indicates the specific genre or type of creative work that an entity is responsible for managing.
-
E.
basisOfWork
Indicates that one entity serves as the foundational source, reference, or inspiration upon which another work is created or derived.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 6:06 p.m.