Triple
T27149944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruskeala Mountain Park |
E682358
|
entity |
| Predicate | materialExtractedHistorically |
P83036
|
FINISHED |
| Object | marble |
—
|
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: marble | Statement: [Ruskeala Mountain Park, materialExtractedHistorically, marble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialExtractedHistorically Context triple: [Ruskeala Mountain Park, materialExtractedHistorically, marble]
-
A.
resourceHistoricallyExtracted
chosen
Indicates that a resource was extracted from a location or entity during some period in the past, but not necessarily in the present.
-
B.
historicallySuppliedOreTo
Indicates that one entity provided ore to another entity as a supplier during a past historical period.
-
C.
historicalMaterial
Indicates that something serves as a source or document providing information or evidence about past events or conditions.
-
D.
historicallyStoredGoods
Indicates that an entity has previously stored certain goods at some time in the past.
-
E.
historicallyQuarriedIn
Indicates that a material or resource was extracted from a particular location during a past historical period.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 9:13 a.m.