Triple
T9520794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morganite |
E229637
|
entity |
| Predicate | opticalCharacter |
P88520
|
FINISHED |
| Object | uniaxial negative |
—
|
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: uniaxial negative | Statement: [Morganite, opticalCharacter, uniaxial negative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticalCharacter Context triple: [Morganite, opticalCharacter, uniaxial negative]
-
A.
recognizesText
Indicates that one entity detects and correctly identifies written or printed text present in or associated with another entity.
-
B.
recognizesDocument
Indicates that one entity acknowledges the validity or authenticity of a document associated with another entity.
-
C.
mediaCharacterization
Indicates how an entity is portrayed, described, or framed by media sources in terms of attributes, tone, or narrative.
-
D.
currentRecognition
Indicates the recognition or acknowledgment an entity presently receives, such as awards, honors, or formal status it currently holds.
-
E.
visionOrSign
Indicates a relationship where something is perceived or presented as a vision, sign, or symbolic manifestation, often conveying a message, omen, or divine indication.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9884dd5c8190b69c178cb2ac75c2 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89f1d748190bf3636bea28d8a37 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:59 p.m.