Triple
T33054261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shemitah |
E845806
|
entity |
| Predicate | pruzbulIntroducedBy |
P175754
|
FINISHED |
| Object | Hillel the Elder |
—
|
NE NERFINISHED |
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: Hillel the Elder | Statement: [Shemitah, pruzbulIntroducedBy, Hillel the Elder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pruzbulIntroducedBy Context triple: [Shemitah, pruzbulIntroducedBy, Hillel the Elder]
-
A.
wereIntroducedBy
Indicates that one entity became known, presented, or brought to the attention of another entity through the action or mediation of a third party.
-
B.
eraIntroducedBy
Indicates that a particular historical or cultural era was initiated or brought into existence by a specific agent, event, or influence.
-
C.
introduced by
Indicates that one entity is presented or made known to another entity through the action or mediation of a third party.
-
D.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
E.
oftenIntroducedBy
Indicates that one entity is frequently presented, mentioned, or brought into context by another entity.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:24 a.m.