Triple
T2553864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microcosmos |
E56687
|
entity |
| Predicate | coAuthorRoleOfDorionSagan |
P2389
|
FINISHED |
| Object | science writer |
—
|
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 writer | Statement: [Microcosmos, coAuthorRoleOfDorionSagan, science writer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coAuthorRoleOfDorionSagan Context triple: [Microcosmos, coAuthorRoleOfDorionSagan, science writer]
-
A.
hasCoauthor
chosen
Indicates that two or more entities have jointly authored the same work or publication.
-
B.
coCreator
Indicates that two or more entities jointly created or produced something together.
-
C.
coDeveloperOf
Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
-
D.
coDiscovererOf
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
E.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.