Triple
T982944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth rotation |
E21210
|
entity |
| Predicate | requiresCorrection |
P21932
|
FINISHED |
| Object | leap seconds |
—
|
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: leap seconds | Statement: [Earth rotation, requiresCorrection, leap seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCorrection Context triple: [Earth rotation, requiresCorrection, leap seconds]
-
A.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
requiresDetectionOf
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
C.
requiresCare
Indicates that one entity depends on another to provide care, attention, or maintenance for its proper functioning or well-being.
-
D.
requiresAlignment
Indicates that one entity depends on another entity being properly aligned or brought into a specified alignment condition before the relationship or action can occur.
-
E.
requiresFinding
Indicates that one entity’s validity, execution, or completion is contingent upon a specific finding or determination being made about 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b49284ac8190b1d7c828d728893c |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b345f890819092b51bf8128da461 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:41 p.m.