Triple
T15515306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born series |
E368819
|
entity |
| Predicate | secondTermCalled |
P118954
|
FINISHED |
| Object | second Born approximation |
—
|
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: second Born approximation | Statement: [Born series, secondTermCalled, second Born approximation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondTermCalled Context triple: [Born series, secondTermCalled, second Born approximation]
-
A.
secondTermSucceededBy
Indicates that the referenced second term is immediately followed or replaced by another term in a sequence or succession.
-
B.
secondTermPrecededBy
Indicates that the second term in a pair occurs earlier in order, time, or sequence than the first term.
-
C.
secondTermEnd
Indicates that the referenced time or event marks the conclusion of the second term in a sequence of terms.
-
D.
secondTermStartYear
Indicates the calendar year in which an entity’s second term in a role, office, or position begins.
-
E.
secondElement
Indicates that one entity is the second element in an ordered pair, sequence, or collection relative to another entity.
- 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_69e04031e62c8190953b61207142af15 |
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, 4:02 a.m.