Triple
T179414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | implicit function theorem |
E3650
|
entity |
| Predicate | concludes |
P7026
|
FINISHED |
| Object | existence of y=g(x) near a point |
—
|
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: existence of y=g(x) near a point | Statement: [implicit function theorem, concludes, existence of y=g(x) near a point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludes Context triple: [implicit function theorem, concludes, existence of y=g(x) near a point]
-
A.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
-
B.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
C.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
D.
convenes
Indicates bringing people or groups together to formally meet, discuss, or deliberate on a particular matter.
-
E.
affirms
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a25900709c8190a65e778936be5dd5 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2582b7f648190b0ef676b8bdc1c65 |
completed | Feb. 28, 2026, 2:51 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.