Triple
T28711583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic ozone hole |
E729843
|
entity |
| Predicate | measuredInUnits |
P12631
|
FINISHED |
| Object | Dobson Units |
—
|
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: Dobson Units | Statement: [Antarctic ozone hole, measuredInUnits, Dobson Units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: measuredInUnits Context triple: [Antarctic ozone hole, measuredInUnits, Dobson Units]
-
A.
measuredAs
Indicates that one entity’s quantity, value, or property is expressed or recorded using another entity as its measurement or unit.
-
B.
unitOfMeasure
chosen
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
-
C.
typeOfMeasure
Indicates that one entity specifies the kind or category of measurement used to quantify or evaluate another entity.
-
D.
numberOfUnits
Indicates the quantity or count of discrete units associated with an entity or relationship.
-
E.
measureOf
Indicates that one entity serves as a quantitative or qualitative assessment or metric describing a property, extent, or magnitude of 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 5:48 a.m.