Triple
T24857598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Editorial Tor |
E622068
|
entity |
| Predicate | hasNotableAuthorPublished |
P10455
|
FINISHED |
| Object | Jorge Luis Borges |
—
|
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: Jorge Luis Borges | Statement: [Editorial Tor, hasNotableAuthorPublished, Jorge Luis Borges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAuthorPublished Context triple: [Editorial Tor, hasNotableAuthorPublished, Jorge Luis Borges]
-
A.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
-
B.
notableAuthorPublished
Indicates that a work was published by an author who is recognized as notable or distinguished.
-
C.
hasNotableWriter
chosen
Indicates that an entity is associated with a writer who is recognized as significant or distinguished in some notable way.
-
D.
hasNotablePublicationType
Indicates that an entity is associated with a publication of a specific notable type or category.
-
E.
hasAuthorPublished
Indicates that a specific author has produced and made publicly available at least one work, such as a book, article, or paper.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 5:21 a.m.