Triple
T34299547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashur |
E880131
|
entity |
| Predicate | receivesOfferingFrom |
P103119
|
FINISHED |
| Object | Assyrian kings |
—
|
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: Assyrian kings | Statement: [Ashur, receivesOfferingFrom, Assyrian kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesOfferingFrom Context triple: [Ashur, receivesOfferingFrom, Assyrian kings]
-
A.
receivesOffering
Indicates that one entity is the recipient of an offering, gift, or sacrifice made by another entity.
-
B.
receivesOfferingsOf
chosen
Indicates that one entity is the recipient of offerings, tributes, or gifts presented by another entity.
-
C.
hasOffering
Indicates that one entity provides, presents, or makes available an offering (such as a product, service, or item) to another entity or context.
-
D.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
E.
rewardOfferedBy
Indicates that a reward is provided or promised by one entity to another, typically as an incentive or compensation for a specific action or outcome.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 1, 2026, 1:57 a.m.