Triple
T3522512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWOS-3 |
E74455
|
entity |
| Predicate | measurementCategory |
P47085
|
FINISHED |
| Object | pressure |
—
|
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: pressure | Statement: [AWOS-3, measurementCategory, pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: measurementCategory Context triple: [AWOS-3, measurementCategory, pressure]
-
A.
measureType
chosen
Indicates the specific kind or category of measurement that characterizes how a quantity or value is assessed.
-
B.
typeOfMeasure
Indicates that one entity specifies the kind or category of measurement used to quantify or evaluate another entity.
-
C.
measurement
Indicates a relationship where one entity quantifies or assigns a value to some property, attribute, or extent of another entity according to a defined scale or standard.
-
D.
measurementOrganization
Indicates that one entity serves as the organization responsible for performing, managing, or overseeing the measurement of another entity or process.
-
E.
measuredAs
Indicates that one entity’s quantity, value, or property is expressed or recorded using another entity as its measurement or unit.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4dd6d48190a5a3f4b86c82b86c |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.