Triple
T9626802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | June Keyes Penguin Habitat |
E232485
|
entity |
| Predicate | hasViewingType |
P31096
|
FINISHED |
| Object | above-water viewing |
—
|
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: above-water viewing | Statement: [June Keyes Penguin Habitat, hasViewingType, above-water viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewingType Context triple: [June Keyes Penguin Habitat, hasViewingType, above-water viewing]
-
A.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
B.
hasViewpointType
chosen
Indicates that something is associated with or characterized by a particular type or category of viewpoint or perspective.
-
C.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
D.
hasViewingSide
Indicates that one entity serves as the side or surface of another entity that is intended to be viewed or observed.
-
E.
viewType
Indicates the specific manner or format in which something is displayed, presented, or visually arranged.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afc9144819084b208c3d04174ba |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.