Triple
T18761773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinai |
E458785
|
entity |
| Predicate | operatesOnGradient |
P133437
|
FINISHED |
| Object | steep incline |
—
|
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: steep incline | Statement: [Sinai, operatesOnGradient, steep incline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnGradient Context triple: [Sinai, operatesOnGradient, steep incline]
-
A.
hasGradient
Indicates that one entity possesses or is characterized by a gradual change in value, intensity, or property across its extent or between two points.
-
B.
usesGradientInformation
Indicates that an entity performs its operation by leveraging gradient (derivative) information, typically to guide optimization or learning steps.
-
C.
hasGradientSection
Indicates that an entity includes a portion or segment where some property changes gradually rather than remaining constant.
-
D.
operatesOnLayer
Indicates that an entity performs actions or functions specifically targeting a particular layer within a layered structure or system.
-
E.
averageGradient
Indicates the mean rate of change (slope) of a quantity over a specified interval or region.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d7fd5008190823bc7e37fdd6669 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:52 a.m.