Triple
T29777346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esmeralda (emerald) |
E755418
|
entity |
| Predicate | mineralFamily |
P168180
|
FINISHED |
| Object | beryl |
—
|
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: beryl | Statement: [Esmeralda (emerald), mineralFamily, beryl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineralFamily Context triple: [Esmeralda (emerald), mineralFamily, beryl]
-
A.
featuresFamilyFrom
Indicates that something includes or presents a family originating from or associated with a specified source.
-
B.
catalogueFamily
Indicates a relationship where an entity is grouped into or associated with a particular catalogue family or classification set.
-
C.
emblemFamily
Indicates that one emblem belongs to, represents, or is associated with a particular family or familial lineage.
-
D.
coreFamily
Indicates that one entity belongs to the other’s immediate (nuclear) family, such as parent, child, or sibling.
-
E.
featuresFamilyName
Indicates that an entity is associated with or displays a particular family name.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f674a363848190814f687a63333026 |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 8:47 p.m.