Triple
T15511935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eka-boron |
E368729
|
entity |
| Predicate | wasUndiscoveredAtTimeOfPrediction |
P118940
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [eka-boron, wasUndiscoveredAtTimeOfPrediction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUndiscoveredAtTimeOfPrediction Context triple: [eka-boron, wasUndiscoveredAtTimeOfPrediction, true]
-
A.
laterDiscovered
Indicates that one entity was discovered or found at a time subsequent to the discovery of another entity.
-
B.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
C.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
D.
wasDiscoveredSoonAfter
Indicates that one event, object, or fact was discovered a relatively short time after another specified reference point or event.
-
E.
rediscoveredAt
Indicates that an entity was found or identified again at a particular time or place after having been lost, forgotten, or unknown.
- 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.