Triple
T29211910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budhan |
E740566
|
entity |
| Predicate | associatedWithGemstone |
P204123
|
FINISHED |
| Object | emerald |
—
|
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: emerald | Statement: [Budhan, associatedWithGemstone, emerald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithGemstone Context triple: [Budhan, associatedWithGemstone, emerald]
-
A.
associatedWithSymbolStones
Indicates a relationship where something is connected or linked to symbol stones, such as being found with them, derived from them, or contextually related to them.
-
B.
relationshipWithJewel
Indicates that one entity has a specified type of relationship or association with a jewel or jewelry item.
-
C.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
-
D.
hasBirthstone
Indicates that a person or entity is associated with a particular gemstone traditionally recognized as their birthstone.
-
E.
preciousStones
Indicates that one entity possesses or is associated with stones that are considered valuable or precious.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a032b2285ac81908826f311a222c749 |
completed | May 12, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_6a032929b8b88190bf7d14d789b38aeb |
completed | May 12, 2026, 1:20 p.m. |
| PDg | Predicate description generation | batch_6a032b21d5b08190bf4690cbf6c1d3de |
completed | May 12, 2026, 1:29 p.m. |
Created at: April 28, 2026, 12:11 p.m.