Triple
T8175025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamioka Observatory |
E190918
|
entity |
| Predicate | shieldingMaterial |
P1272
|
FINISHED |
| Object | rock overburden |
—
|
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: rock overburden | Statement: [Kamioka Observatory, shieldingMaterial, rock overburden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shieldingMaterial Context triple: [Kamioka Observatory, shieldingMaterial, rock overburden]
-
A.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
B.
heatShieldType
Indicates the specific kind or category of heat shield associated with an object or system.
-
C.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
primaryTargetMaterial
Indicates the material that serves as the main or principal target in a given process, action, or interaction.
-
E.
heatShieldThickness
Indicates the thickness of a protective heat shield used to guard an object from high temperatures or thermal loads.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb480a7ac4819088fabd5bec6ba2e5 |
completed | March 31, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.