Triple
T29314193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammett sigma constants |
E743332
|
entity |
| Predicate | zeroPointReference |
P65427
|
FINISHED |
| Object | hydrogen substituent |
—
|
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: hydrogen substituent | Statement: [Hammett sigma constants, zeroPointReference, hydrogen substituent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zeroPointReference Context triple: [Hammett sigma constants, zeroPointReference, hydrogen substituent]
-
A.
zeroDefinition
Indicates that something has no defined value, quantity, or specification within the given context.
-
B.
formsZeroPointFor
chosen
Indicates that one entity serves as the reference or origin point (zero point) for measuring or defining another entity.
-
C.
referenceMeridian
Indicates that one location, measurement, or coordinate system is defined or interpreted relative to a specified meridian used as its longitudinal reference.
-
D.
zeroConcept
Indicates a conceptual or abstract entity that has no concrete instances or realizations in the given context.
-
E.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665e8645881908b929b57b866b6d3 |
completed | May 2, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:18 p.m.