Triple
T2815334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euler’s formula for complex exponentials |
E54268
|
entity |
| Predicate | canBeExtendedTo |
P17547
|
FINISHED |
| Object | complex \theta |
—
|
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: complex \theta | Statement: [Euler’s formula for complex exponentials, canBeExtendedTo, complex \theta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeExtendedTo Context triple: [Euler’s formula for complex exponentials, canBeExtendedTo, complex \theta]
-
A.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
B.
extendsTo
Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
-
C.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
-
D.
canBeAugmentedWith
chosen
Indicates that one entity is capable of being enhanced, expanded, or supplemented by another entity.
-
E.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4d29488190a32461906dd9ea7e |
completed | March 7, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.