Triple
T32043596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landau collision operator |
E818277
|
entity |
| Predicate | drivesSystemTo |
P145827
|
FINISHED |
| Object | Maxwellian equilibrium distribution |
—
|
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: Maxwellian equilibrium distribution | Statement: [Landau collision operator, drivesSystemTo, Maxwellian equilibrium distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivesSystemTo Context triple: [Landau collision operator, drivesSystemTo, Maxwellian equilibrium distribution]
-
A.
drives
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
-
B.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
C.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
D.
demonDrivenTo
Indicates that a demon compels, motivates, or forces an entity to move toward or act upon a particular target or goal.
-
E.
drivenTo
chosen
Indicates that one entity causes or compels another entity to move or act toward a particular state, goal, or location.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 12:19 a.m.