Triple
T15511938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eka-boron |
E368729
|
entity |
| Predicate | correspondingElementDiscoveredIn |
P118942
|
FINISHED |
| Object | 1879 |
—
|
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: 1879 | Statement: [eka-boron, correspondingElementDiscoveredIn, 1879]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondingElementDiscoveredIn Context triple: [eka-boron, correspondingElementDiscoveredIn, 1879]
-
A.
associatedWithElement
Indicates a relationship where one entity is linked or connected to a particular element, such that the element is relevant to, involved in, or characteristic of that entity.
-
B.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
C.
discoveredOnPropertyOf
Indicates that something was found or detected while located on the property owned or controlled by a particular entity.
-
D.
discoveredWith
Indicates that one entity was found, detected, or identified using another entity as the means, tool, method, or accompanying context of discovery.
-
E.
discoveredResource
Indicates that an entity has found, identified, or uncovered a particular resource.
- F. None of above. chosen
Provenance (4 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04030c0208190a1931ea130075603 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:56 a.m.