Triple
T13507207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fibonacci heap |
E321043
|
entity |
| Predicate | cascadingCutTriggeredBy |
P78461
|
FINISHED |
| Object | second child cut from a node |
—
|
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: second child cut from a node | Statement: [Fibonacci heap, cascadingCutTriggeredBy, second child cut from a node]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cascadingCutTriggeredBy Context triple: [Fibonacci heap, cascadingCutTriggeredBy, second child cut from a node]
-
A.
isCascading
chosen
Indicates that one event, action, or effect triggers a chain of subsequent related events, actions, or effects.
-
B.
partOfCascade
Indicates that one event, process, or component functions as a step or segment within a larger sequential cascade.
-
C.
crossCut
Indicates that one entity intersects or passes through another, typically cutting across it from one side to the other.
-
D.
hasCut
Indicates that one entity has made or possesses a cut in, on, or through another entity.
-
E.
triggeredFrom
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf8259a08190ada13c4a3078f07d |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.