Triple
T15961340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korteweg–De Vries equation |
E387064
|
entity |
| Predicate | hasLaxPair |
P120614
|
FINISHED |
| Object | L_t = [P,L] with L = -\partial_x^2 + u(x,t) |
—
|
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: L_t = [P,L] with L = -\partial_x^2 + u(x,t) | Statement: [Korteweg–De Vries equation, hasLaxPair, L_t = [P,L] with L = -\partial_x^2 + u(x,t)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaxPair Context triple: [Korteweg–De Vries equation, hasLaxPair, L_t = [P,L] with L = -\partial_x^2 + u(x,t)]
-
A.
isPairOf
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
-
B.
hasBracket
Indicates that one entity possesses, includes, or is associated with a bracket component or structure.
-
C.
hasLacing
Indicates a relationship where one entity is fastened, joined, or secured to another using laces or a lacing mechanism.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
hasDouble
Indicates that an entity possesses or is associated with a counterpart that is a duplicate or closely similar version of it.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:53 a.m.