Triple
T29013715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point of View (short story) |
E737241
|
entity |
| Predicate | hasAnthologyAuthor |
P4244
|
FINISHED |
| Object | Isaac Asimov |
—
|
NE NERFINISHED |
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: Isaac Asimov | Statement: [Point of View (short story), hasAnthologyAuthor, Isaac Asimov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnthologyAuthor Context triple: [Point of View (short story), hasAnthologyAuthor, Isaac Asimov]
-
A.
hasAnthologyRelation
Indicates that there is a relationship between entities based on their inclusion in, contribution to, or association with the same anthology or collected work.
-
B.
hasAnthologyFormat
Indicates that an entity is presented or structured in the form of an anthology (a collection of distinct works or pieces).
-
C.
hasAuthorInCatalog
Indicates that an item in a catalog is associated with a specific author recorded in that catalog.
-
D.
hasAuthorOf
Indicates that one entity is the author or creator of another entity (such as a work, document, or publication).
-
E.
hasAuthor
chosen
Indicates that an entity is written or created by a specific author.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 9:44 a.m.