Triple
T32530992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moses at the burning bush |
E831451
|
entity |
| Predicate | MosesOccupationAtTime |
P60589
|
FINISHED |
| Object | shepherd |
—
|
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: shepherd | Statement: [Moses at the burning bush, MosesOccupationAtTime, shepherd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MosesOccupationAtTime Context triple: [Moses at the burning bush, MosesOccupationAtTime, shepherd]
-
A.
MosesResponse
Indicates how Moses reacts, replies, or responds in a given situation or interaction.
-
B.
MosesObjection
Indicates that Moses raises an objection, protest, or resistance in response to a command, request, or situation.
-
C.
offeredByMoses
Indicates that something (such as a law, commandment, or offering) is presented, given, or instituted by Moses.
-
D.
viewsMosesAs
Indicates that one entity regards or considers another entity in the role, status, or identity of Moses.
-
E.
earliestMajorOccupation
chosen
Indicates the earliest significant occupation or professional role held by an entity in its life or career timeline.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c51cafe4819095e91e733b358c90 |
completed | May 3, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:01 a.m.