Triple
T15850013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaronites |
E384308
|
entity |
| Predicate | receivedPortion |
P120757
|
FINISHED |
| Object | portions of sacrifices |
—
|
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: portions of sacrifices | Statement: [Aaronites, receivedPortion, portions of sacrifices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedPortion Context triple: [Aaronites, receivedPortion, portions of sacrifices]
-
A.
receivedTransmissionOf
Indicates that one entity has obtained or been sent a transmission (such as a message, signal, or data) originating from another entity.
-
B.
handlesPortionOf
Indicates that one entity is responsible for managing or dealing with a specific part or subset of another entity or task.
-
C.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified entity.
-
D.
receivedPromiseAbout
Indicates that one entity has been given an assurance or commitment concerning another entity or event by some source.
-
E.
reconstructedPortion
Indicates that a portion of an object, structure, or data has been rebuilt or restored from partial, damaged, or missing original information.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.