Triple
T6833013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laplace method |
E157382
|
entity |
| Predicate | x0 |
P37345
|
FINISHED |
| Object | point where f(x) attains its maximum on [a,b] |
—
|
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: point where f(x) attains its maximum on [a,b] | Statement: [Laplace method, x0, point where f(x) attains its maximum on [a,b]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: x0 Context triple: [Laplace method, x0, point where f(x) attains its maximum on [a,b]]
-
A.
export
Indicates that one entity sends goods, services, or data out from its own domain or territory to another entity or external destination.
-
B.
in
chosen
Indicates that one entity is located within the spatial, temporal, or conceptual bounds of another entity.
-
C.
from
Indicates that something originates, is sent, or is derived from a particular source or starting point.
-
D.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
E.
B_0
Indicates a basic or unspecified binary relationship between two entities, where the exact nature of the connection is not further defined.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.