Triple
T7833409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyapunov time |
E181628
|
entity |
| Predicate | helpsDescribe |
P264
|
FINISHED |
| Object | limits of long-term prediction |
—
|
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: limits of long-term prediction | Statement: [Lyapunov time, helpsDescribe, limits of long-term prediction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsDescribe Context triple: [Lyapunov time, helpsDescribe, limits of long-term prediction]
-
A.
describes
chosen
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
B.
helpsIdentify
Indicates a relationship where one entity serves to distinguish, recognize, or determine the identity or characteristics of another entity.
-
C.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
D.
settingDescription
Indicates the descriptive details or characteristics that define the context or environment in which something occurs.
-
E.
toolDescribed
Indicates that one entity provides a description or explanation of a tool associated with another entity.
- 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_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. |
Created at: March 30, 2026, 4:45 p.m.