Triple
T2733341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opal |
E60368
|
entity |
| Predicate | hasFracture |
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: [Opal, hasFracture, conchoidal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFracture Context triple: [Opal, hasFracture, conchoidal]
-
A.
fracture
chosen
Indicates a relationship where an object or material is broken or cracked into parts, typically due to applied stress or impact.
-
B.
hasInjuries
Indicates that an entity has sustained one or more physical or bodily injuries.
-
C.
hasCrack
Indicates that one entity possesses or exhibits a crack, fracture, or split in its structure or surface.
-
D.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
E.
hasDam
Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaf175808190acbbb3873c7c3f67 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.