Triple
T25598875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grotta Gigante |
E641730
|
entity |
| Predicate | hasFirstExplorationYear |
P173666
|
FINISHED |
| Object | 1840 |
—
|
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: 1840 | Statement: [Grotta Gigante, hasFirstExplorationYear, 1840]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstExplorationYear Context triple: [Grotta Gigante, hasFirstExplorationYear, 1840]
-
A.
hasExploration
Indicates that one entity engages in, is associated with, or possesses an activity or process of exploration in relation to another entity or context.
-
B.
hasFirstCohortYear
Indicates the year in which the first cohort associated with an entity began or was established.
-
C.
hasFirstProofYear
Indicates the year in which something was first proven or formally demonstrated to be true.
-
D.
hasHistoricalPeriodOfExploration
Indicates that an entity is associated with, or characterized by, a specific historical period during which exploration activities took place.
-
E.
isEarlyExplorationOf
Indicates that one entity represents an initial or preliminary investigation, study, or probing of another entity before more advanced or detailed work occurs.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 21, 2026, 4:30 p.m.