Triple
T26205076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | norepinephrine |
E655337
|
entity |
| Predicate | isPolar |
P160366
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [norepinephrine, isPolar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPolar Context triple: [norepinephrine, isPolar, true]
-
A.
hasPolarSetting
Indicates that something is configured or oriented according to a polar coordinate or polar reference system.
-
B.
hasPolarRadius
Indicates that an entity possesses a specific radius measured from its center to its pole, typically used for spheroidal or planetary bodies.
-
C.
hasPolarCoverage
Indicates that an entity includes or provides coverage, presence, or applicability in polar regions.
-
D.
hasPolarEquation
Indicates that an entity is associated with, or can be represented by, a specific equation expressed in polar coordinates.
-
E.
polarForm
Indicates that a complex number or vector is represented in polar coordinates, specifying its magnitude and angle relative to a reference axis.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cde512c819094036b09613ff330 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 8:50 p.m.