Triple
T6335808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S41 |
E142487
|
entity |
| Predicate | directionOfOperation |
P9946
|
FINISHED |
| Object | clockwise |
—
|
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: clockwise | Statement: [S41, directionOfOperation, clockwise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfOperation Context triple: [S41, directionOfOperation, clockwise]
-
A.
directionalOperation
chosen
Indicates an operation whose effect depends on or is applied along a specific direction or orientation between entities.
-
B.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
C.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
D.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
-
E.
operatorDuringOperation
Indicates that an operator is the one performing or responsible for an operation during its execution.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654a88a881908d5cb2aa7f22c4c7 |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.