Triple
T36691521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | allanite-(Ce) |
E905967
|
entity |
| Predicate | hasOpticalProperty |
P32006
|
FINISHED |
| Object | strong pleochroism |
—
|
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: strong pleochroism | Statement: [allanite-(Ce), hasOpticalProperty, strong pleochroism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpticalProperty Context triple: [allanite-(Ce), hasOpticalProperty, strong pleochroism]
-
A.
opticalProperty
chosen
Indicates a relationship where an entity has or is characterized by a specific optical property, such as how it interacts with or responds to light.
-
B.
hasOpticalElement
Indicates that one entity includes, contains, or is equipped with a specific optical element as a component or part.
-
C.
hasOpticalChannels
Indicates that an entity possesses one or more optical communication or signal-transmission channels.
-
D.
hasIlluminationProperty
Indicates that one entity possesses or is characterized by a specific illumination-related attribute or quality in relation to another.
-
E.
usesOpticsType
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:12 p.m.