Triple
T24981764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nethanel son of Zuar |
E625186
|
entity |
| Predicate | offeringDescribedIn |
P519
|
FINISHED |
| Object | Numbers 7:18–23 |
—
|
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: Numbers 7:18–23 | Statement: [Nethanel son of Zuar, offeringDescribedIn, Numbers 7:18–23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeringDescribedIn Context triple: [Nethanel son of Zuar, offeringDescribedIn, Numbers 7:18–23]
-
A.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
B.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
C.
describedIn
chosen
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
D.
offeringMayInclude
Indicates that a particular offering can contain, comprise, or be associated with one or more specified components, items, or elements.
-
E.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 18, 2026, 6:02 a.m.