Triple
T4707733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwin McMillan |
E104431
|
entity |
| Predicate | co-invented |
P1858
|
FINISHED |
| Object | synchrotron |
—
|
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: synchrotron | Statement: [Edwin McMillan, co-invented, synchrotron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: co-invented Context triple: [Edwin McMillan, co-invented, synchrotron]
-
A.
co-discoveredWith
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
B.
coInventorWith
chosen
Indicates that two or more entities jointly invented or created the same invention.
-
C.
invention
Indicates that one entity is the creator or originator of another entity, typically a device, method, or idea.
-
D.
developedInParallelWith
Indicates that two or more things were created or progressed during the same time period, with their development processes occurring concurrently rather than sequentially.
-
E.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:17 p.m.