Triple
T37704070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ti:sapphire laser |
E939151
|
entity |
| Predicate | hostCrystal |
P135720
|
FINISHED |
| Object | sapphire |
—
|
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: sapphire | Statement: [Ti:sapphire laser, hostCrystal, sapphire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCrystal Context triple: [Ti:sapphire laser, hostCrystal, sapphire]
-
A.
hostCraton
Indicates that one geological feature or unit is situated within or supported by a cratonic block (ancient, stable part of the continental lithosphere).
-
B.
hostRock
Indicates that one rock body serves as the surrounding or enclosing rock in which another geological feature (such as an ore deposit, vein, or intrusion) occurs.
-
C.
hostMonarch
Indicates that one entity serves as the reigning monarch or royal ruler presiding over another entity (such as a realm, territory, or people).
-
D.
hostStar
Indicates that one celestial object serves as the primary star around which another object, such as a planet or system, is associated or orbits.
-
E.
hostLatticeFor
chosen
Indicates that one entity serves as the structural lattice framework within which another entity is incorporated, embedded, or accommodated.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.