Triple
T13001297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSI 2* |
E322174
|
entity |
| Predicate | jumpOff |
P107770
|
FINISHED |
| Object | used to break ties on faults and 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: used to break ties on faults and time | Statement: [CSI 2*, jumpOff, used to break ties on faults and time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jumpOff Context triple: [CSI 2*, jumpOff, used to break ties on faults and time]
-
A.
jumpLength
Indicates the distance covered by an entity in a single jump.
-
B.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
-
C.
fallsFrom
Indicates that one entity moves downward or drops starting from the location or position of another entity.
-
D.
escapeLocation
Indicates that an entity moves away from or leaves a location to avoid danger, capture, or an undesirable situation.
-
E.
fallLocation
Indicates the place or area where an entity falls or ends up after falling.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9828748190b2ad9ea29180b7d3 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e74283c819082e69ac3554fa7d8 |
completed | April 10, 2026, 10:49 p.m. |
Created at: April 9, 2026, 8:47 p.m.