Triple
T16489154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine observatories |
E400524
|
entity |
| Predicate | measure |
P43487
|
FINISHED |
| Object | temperature |
—
|
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: temperature | Statement: [Marine observatories, measure, temperature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: measure Context triple: [Marine observatories, measure, temperature]
-
A.
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.
-
B.
measureOf
Indicates that one entity serves as a quantitative or qualitative assessment or metric describing a property, extent, or magnitude of another entity.
-
C.
measureType
Indicates the specific kind or category of measurement that characterizes how a quantity or value is assessed.
-
D.
measured
chosen
Indicates that one entity has determined or quantified a property, amount, or extent of another entity using some standard or instrument.
-
E.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e2e3bf88190ba6eac85a79e5ac8 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:13 a.m.