Triple
T23801556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conformal Invariants |
E588686
|
entity |
| Predicate | hasAuthorOfOtherNotableWork |
P142856
|
FINISHED |
| Object | Complex Analysis |
—
|
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: Complex Analysis | Statement: [Conformal Invariants, hasAuthorOfOtherNotableWork, Complex Analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorOfOtherNotableWork Context triple: [Conformal Invariants, hasAuthorOfOtherNotableWork, Complex Analysis]
-
A.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
-
B.
hasAuthorAlsoKnownFor
chosen
Indicates that the author of a work is additionally recognized or notable for another specific work, role, or achievement.
-
C.
hasArtistOfNotableWork
Indicates that an entity is associated with the artist who created a notable work related to that entity.
-
D.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
E.
hasMotherNotableWork
Indicates that the mother of the subject entity created, authored, or is best known for the specified work.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c74e430481909debd10c71785912 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:53 p.m.