Triple
T23347137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | buckminsterfullerene |
E591897
|
entity |
| Predicate | isFirstDiscoveredMemberOf |
P121961
|
FINISHED |
| Object | 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: fullerenes | Statement: [buckminsterfullerene, isFirstDiscoveredMemberOf, fullerenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFirstDiscoveredMemberOf Context triple: [buckminsterfullerene, isFirstDiscoveredMemberOf, fullerenes]
-
A.
hasFirstDiscoveredMember
Indicates that a group, category, or collection is linked to the specific member that was first discovered within it.
-
B.
firstMember
chosen
Indicates that one entity is the first member or element in an ordered collection or group relative to the others.
-
C.
discoveredBefore
Indicates that one entity was discovered earlier in time than another entity.
-
D.
isFirstToInclude
Indicates that an entity is the earliest or original one to incorporate or contain another specified entity, feature, or element.
-
E.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19837874481908f1a530261a34819 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:19 p.m.