Triple
T1929294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devonian Fossil Gorge |
E40904
|
entity |
| Predicate | furtherExposedBy |
P25434
|
FINISHED |
| Object | 2008 Iowa flood |
—
|
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: 2008 Iowa flood | Statement: [Devonian Fossil Gorge, furtherExposedBy, 2008 Iowa flood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furtherExposedBy Context triple: [Devonian Fossil Gorge, furtherExposedBy, 2008 Iowa flood]
-
A.
exposed
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
B.
exposes
chosen
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
C.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
-
D.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
-
E.
gainedVisibilityThrough
Indicates that one entity became more visible, prominent, or well-known as a result of another entity or mechanism.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb266dcb4819090be83556615d0db |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.