Triple
T24484642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larder Lake gold camp |
E617471
|
entity |
| Predicate | hostStructure |
P156481
|
FINISHED |
| Object | quartz-carbonate veins |
—
|
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: quartz-carbonate veins | Statement: [Larder Lake gold camp, hostStructure, quartz-carbonate veins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostStructure Context triple: [Larder Lake gold camp, hostStructure, quartz-carbonate veins]
-
A.
hipStructure
Indicates a structural or anatomical relationship involving the hip, such as how its components are organized, connected, or configured.
-
B.
standStructure
Indicates that one entity is a vertical support or upright structural element for another entity.
-
C.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
-
D.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
E.
hostBuilding
Indicates that one entity serves as the building or physical structure that houses, contains, or accommodates another entity.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:21 a.m.