Triple
T15446703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icehouse Canyon |
E370040
|
entity |
| Predicate | hasRemnantsOf |
P16216
|
FINISHED |
| Object | historic cabins |
—
|
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: historic cabins | Statement: [Icehouse Canyon, hasRemnantsOf, historic cabins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemnantsOf Context triple: [Icehouse Canyon, hasRemnantsOf, historic cabins]
-
A.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
B.
hasRemainsOf
chosen
Indicates that one entity physically contains, preserves, or is associated with the leftover physical traces or remnants of another entity.
-
C.
lastRemnantOf
Indicates that one entity is the sole remaining instance or surviving part of another entity, after all similar or related instances have disappeared.
-
D.
isYoungerRemnantOf
Indicates that one entity is the surviving, younger portion or successor of another entity that existed earlier and has largely disappeared or transformed.
-
E.
remnantsInclude
Indicates that the remaining parts or leftovers of one entity contain or consist 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef767b4819099f2c0919a158321 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.