Triple
T25976152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liouville–von Neumann equation |
E645944
|
entity |
| Predicate | isFirstOrderIn |
P159862
|
FINISHED |
| Object | time |
—
|
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: time | Statement: [Liouville–von Neumann equation, isFirstOrderIn, time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFirstOrderIn Context triple: [Liouville–von Neumann equation, isFirstOrderIn, time]
-
A.
isFirstOrderMethod
Indicates that a method or procedure operates at the first order, typically using only first-order logic or first-order derivatives without involving higher-order constructs.
-
B.
isOrderIn
Indicates that one entity is contained within or belongs to a specified order or sequence of entities.
-
C.
isFirstSingleFrom
Indicates that one musical work is the first single released from another work, typically an album or larger recording project.
-
D.
isFirstInCategory
Indicates that an entity is the earliest or primary member within a defined category or group.
-
E.
isOldestOrderOf
Indicates that one order is the earliest or first created among a set of related orders for a given context or entity.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6050973a0819082e9b568175b7991 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 8:52 a.m.