Triple
T1243570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephron the Hittite |
E26712
|
entity |
| Predicate | priceDescribedAs |
P7794
|
FINISHED |
| Object | four hundred shekels of silver |
—
|
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: four hundred shekels of silver | Statement: [Ephron the Hittite, priceDescribedAs, four hundred shekels of silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceDescribedAs Context triple: [Ephron the Hittite, priceDescribedAs, four hundred shekels of silver]
-
A.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
B.
priceReference
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
-
C.
priceRelationship
Indicates a comparative relationship between the prices of two entities, such as one being higher, lower, or equal to the other.
-
D.
priceCategory
Indicates the classification of an item or service based on its price level or cost range.
-
E.
purchasePrice
chosen
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf636e208190a4d56806db61916c |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.