Triple
T15515305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born series |
E368819
|
entity |
| Predicate | firstTermCalled |
P46246
|
FINISHED |
| Object | first 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: first Born approximation | Statement: [Born series, firstTermCalled, first Born approximation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTermCalled Context triple: [Born series, firstTermCalled, first Born approximation]
-
A.
firstTermStart
Indicates that an entity marks the starting point or initial term in an ordered sequence, period, or agreement.
-
B.
firstTerms
chosen
Indicates that the related entities are the initial elements or starting terms in a sequence, series, or ordered collection.
-
C.
firstClauseKnownAs
Indicates that one clause in a legal or formal document is referred to or designated by a particular name or label.
-
D.
firstOrdinary
Indicates that the subject is the first entity to hold or occupy an ordinary (non-special, standard) position, role, or status in a given sequence or context.
-
E.
firstFactor
Indicates that one entity is the first factor (multiplicand) in a multiplication relationship with another 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_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. |
Created at: April 10, 2026, 4:02 a.m.