Triple
T7833401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyapunov time |
E181628
|
entity |
| Predicate | where |
P79270
|
FINISHED |
| Object | λ_max is the largest Lyapunov exponent |
—
|
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: λ_max is the largest Lyapunov exponent | Statement: [Lyapunov time, where, λ_max is the largest Lyapunov exponent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: where Context triple: [Lyapunov time, where, λ_max is the largest Lyapunov exponent]
-
A.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
B.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
E.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb064a47648190af2ca2b336584a92 |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:45 p.m.