Triple
T19779585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Giovanni Battista Church, Mogno |
E475094
|
entity |
| Predicate | primaryStoneSource |
P66958
|
FINISHED |
| Object | local Ticino gneiss |
—
|
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: local Ticino gneiss | Statement: [San Giovanni Battista Church, Mogno, primaryStoneSource, local Ticino gneiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStoneSource Context triple: [San Giovanni Battista Church, Mogno, primaryStoneSource, local Ticino gneiss]
-
A.
originalStoneName
Indicates that an entity has or is associated with the original or primary name assigned to a particular stone.
-
B.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
-
C.
geologicalOriginOfStones
chosen
Indicates the geological source or formation process from which particular stones originate.
-
D.
madeOfSingleStone
Indicates that something is constructed or formed from a single, continuous piece of stone rather than multiple joined stone elements.
-
E.
stoneQuality
Indicates the quality or grade assigned to a stone in terms of its characteristics or condition.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538230488190b45cd8aaec658f7f |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.