Triple
T1795393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond |
E39591
|
entity |
| Predicate | fracture |
P32005
|
FINISHED |
| Object | conchoidal |
—
|
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: conchoidal | Statement: [Diamond, fracture, conchoidal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fracture Context triple: [Diamond, fracture, conchoidal]
-
A.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
B.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
C.
injuryType
Indicates the specific kind or category of injury associated with an entity or event.
-
D.
spontaneouslyBrokenBy
Indicates that a symmetry or property is not explicitly violated by the underlying laws but is instead broken by the system’s ground state or configuration due to spontaneous symmetry breaking caused by the specified entity or mechanism.
-
E.
fallsOn
Indicates that one entity descends due to gravity and comes to rest upon the surface of 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab61b5c8988190bb2b46182a4eb5b4 |
completed | March 6, 2026, 11:22 p.m. |
Created at: March 4, 2026, 7:32 p.m.