Triple
T27134896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESCA |
E681654
|
entity |
| Predicate | quantificationMethod |
P120447
|
FINISHED |
| Object | sensitivity factor calibration |
—
|
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: sensitivity factor calibration | Statement: [ESCA, quantificationMethod, sensitivity factor calibration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quantificationMethod Context triple: [ESCA, quantificationMethod, sensitivity factor calibration]
-
A.
quantificationType
Indicates the specific kind or category of quantity or measurement being applied in a given context.
-
B.
quantifies
Indicates that one entity expresses or specifies the amount, number, or degree of another entity.
-
C.
usesQuantification
chosen
Indicates that one entity employs or applies a system of quantification (such as numerical or measurable assessment) to another entity or context.
-
D.
quantifiesOver
Indicates that one entity expresses a quantity, measurement, or numerical specification that applies to or ranges over another entity.
-
E.
quantifierProperty
Indicates that a quantifier is associated with a specific property or constraint that it quantifies over.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62479bbb88190bcad383443cbd638 |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:06 a.m.