Triple
T13682865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump Week |
E328044
|
entity |
| Predicate | requiresPriorPhase |
P65161
|
FINISHED |
| Object | Ground Week |
—
|
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: Ground Week | Statement: [Jump Week, requiresPriorPhase, Ground Week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPriorPhase Context triple: [Jump Week, requiresPriorPhase, Ground Week]
-
A.
hasEarlierPhase
chosen
Indicates that one phase occurs before another phase in a process or sequence.
-
B.
requiresPriorJudicialApproval
Indicates that an action or decision can only be taken if it has been previously reviewed and authorized by a judicial authority.
-
C.
previouslyRequired
Indicates that one entity was required or necessary before another entity, typically as a prerequisite condition or step.
-
D.
requiresInitiationIn
Indicates that one entity must be initiated, started, or activated within the context, scope, or environment defined by another entity.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.