Triple
T15511920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eka-boron |
E368729
|
entity |
| Predicate | predictedUsing |
P43685
|
FINISHED |
| Object | periodic law |
—
|
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: periodic law | Statement: [eka-boron, predictedUsing, periodic law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predictedUsing Context triple: [eka-boron, predictedUsing, periodic law]
-
A.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
B.
predictionBy
Indicates that one entity serves as the source or author of a prediction made about another entity or outcome.
-
C.
predictionType
Indicates the kind or category of prediction being made about an entity or event.
-
D.
forecastUsing
chosen
Indicates that one entity generates or derives a forecast by using information, methods, or data from another entity.
-
E.
predictionAlgorithm
Indicates a relationship where an algorithm generates predictions or forecasts about outcomes based on input data or observed patterns.
- 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_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. |
Created at: April 10, 2026, 3:56 a.m.