Triple
T4907557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesvos Petrified Forest Geopark |
E109948
|
entity |
| Predicate | mainFossilType |
P40905
|
FINISHED |
| Object | petrified wood |
—
|
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: petrified wood | Statement: [Lesvos Petrified Forest Geopark, mainFossilType, petrified wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFossilType Context triple: [Lesvos Petrified Forest Geopark, mainFossilType, petrified wood]
-
A.
fossilGroup
Indicates that one entity is classified as belonging to a particular fossil group or assemblage associated with another entity.
-
B.
fossilSiteType
chosen
Indicates the specific type or classification of a site where fossils are found or collected.
-
C.
containsFossilsOf
Indicates that one entity (typically a geological formation, rock, or sample) includes fossil remains or traces belonging to another entity (an organism or taxon).
-
D.
fossilContent
Indicates that one entity contains, preserves, or is characterized by the fossils of another entity.
-
E.
stateFossil
Indicates that a particular fossil has been officially designated as the representative state fossil of a given state.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e7452d481909078a0027e2a4566 |
completed | March 20, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.