Triple
T3607767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hyperpyron |
E76413
|
entity |
| Predicate | purityAtIntroduction |
P6859
|
FINISHED |
| Object | high gold fineness |
—
|
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: high gold fineness | Statement: [hyperpyron, purityAtIntroduction, high gold fineness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purityAtIntroduction Context triple: [hyperpyron, purityAtIntroduction, high gold fineness]
-
A.
purity
chosen
Indicates that an entity possesses a high degree of cleanliness, integrity, or freedom from contamination, corruption, or mixed elements.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
oftenIntroducedBy
Indicates that one entity is frequently presented, mentioned, or brought into context by another entity.
-
D.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
E.
introducedDuring
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc228e24481909ae6a1e4ad796917 |
completed | March 8, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.