Triple
T15580033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George VI Ice Shelf |
E374468
|
entity |
| Predicate | hasSurfaceFeatures |
P47694
|
FINISHED |
| Object | crevasses |
—
|
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: crevasses | Statement: [George VI Ice Shelf, hasSurfaceFeatures, crevasses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceFeatures Context triple: [George VI Ice Shelf, hasSurfaceFeatures, crevasses]
-
A.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
-
B.
hasSurfaceLevel
Indicates that one entity possesses or is characterized by a particular degree or measure of surface level (e.g., depth, detail, or superficiality).
-
C.
surfaceFeatureOf
chosen
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
D.
hasSurfaceSections
Indicates that an entity is composed of or divided into distinct sections or parts of its surface.
-
E.
hasSurfaceQuality
Indicates that one entity possesses a particular characteristic or condition of its surface.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e24064c8190b132c3092877fbfa |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.