Triple
T25077066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Rock |
E628078
|
entity |
| Predicate | containedAncientLakeShorelines |
P169206
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fort Rock, containedAncientLakeShorelines, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedAncientLakeShorelines Context triple: [Fort Rock, containedAncientLakeShorelines, true]
-
A.
consideredAncientLake
Indicates that a body of water is regarded as an ancient lake, typically having existed continuously for a very long geological timespan.
-
B.
locatedInFormerLake
Indicates that an entity is situated within the area that was once occupied by a lake that no longer exists.
-
C.
hasHydrocarbonLakes
Indicates that the subject possesses or contains lakes composed primarily of liquid hydrocarbons rather than water.
-
D.
hasProglacialLake
Indicates that a glacier or ice sheet is or was associated with a lake formed directly in front of it by meltwater or ice-dammed water.
-
E.
hasSubglacialLake
Indicates that a glacier or ice sheet contains a lake of liquid water located beneath its ice.
- F. None of above. chosen
Provenance (4 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 18, 2026, 6:21 a.m.