Triple
T3302911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petoskey stones |
E69375
|
entity |
| Predicate | environmentOfFormation |
P9688
|
FINISHED |
| Object | shallow warm sea |
—
|
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: shallow warm sea | Statement: [Petoskey stones, environmentOfFormation, shallow warm sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentOfFormation Context triple: [Petoskey stones, environmentOfFormation, shallow warm sea]
-
A.
depositionalEnvironment
chosen
Indicates the natural setting or conditions under which sediments were originally deposited.
-
B.
geologicalFormationProcess
Indicates the natural geological process or set of processes by which a particular geological formation came into existence.
-
C.
primaryFormation
Indicates that one entity serves as the main or original formation or structural configuration associated with another entity.
-
D.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
E.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c662308190aad8b2a93e1c8a5c |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.