Triple
T12254282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IUCN Category III |
E292058
|
entity |
| Predicate | typicallySize |
P28652
|
FINISHED |
| Object | relatively small protected areas |
—
|
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: relatively small protected areas | Statement: [IUCN Category III, typicallySize, relatively small protected areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallySize Context triple: [IUCN Category III, typicallySize, relatively small protected areas]
-
A.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
B.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
C.
typicalCastSize
Indicates the usual or standard number of cast members involved in a production or performance.
-
D.
sizeDescription
chosen
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
E.
typicalPanelSize
Indicates the usual or standard dimensions associated with a given panel.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.