Triple
T24056929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Curl |
E595830
|
entity |
| Predicate | co-authorOf |
P2389
|
FINISHED |
| Object | scientific papers on fullerenes |
—
|
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: scientific papers on fullerenes | Statement: [Robert Curl, co-authorOf, scientific papers on fullerenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: co-authorOf Context triple: [Robert Curl, co-authorOf, scientific papers on fullerenes]
-
A.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
B.
hasCoauthor
chosen
Indicates that two or more entities have jointly authored the same work or publication.
-
C.
co-editedWith
Indicates that two or more entities jointly served as editors of the same work or publication.
-
D.
coAuthorNationality
Indicates that two or more co-authors of a work share the same nationality or have nationalities being related in the context of their co-authorship.
-
E.
coAuthorshipType
Indicates the specific nature or category of the collaborative authorship relationship between two or more contributors.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da50d6108190a36bffaa475c8b93 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:34 p.m.