Triple
T13026826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Agagite |
E326328
|
entity |
| Predicate | traditionallyUnderstoodIn |
P39675
|
FINISHED |
| Object | rabbinic literature |
—
|
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: rabbinic literature | Statement: [the Agagite, traditionallyUnderstoodIn, rabbinic literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyUnderstoodIn Context triple: [the Agagite, traditionallyUnderstoodIn, rabbinic literature]
-
A.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
B.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
C.
hasTraditionalInterpretation
chosen
Indicates that something is associated with or understood according to a long-established or customary interpretation.
-
D.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
E.
unifiedByTradition
Indicates that multiple entities are brought together or closely connected through a shared tradition or customary practice.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efc07488190a15f3e41ea2db45c |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:53 p.m.