Triple
T16856828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1568 Edict of Torda |
E409803
|
entity |
| Predicate | didNotExtendTo |
P10124
|
FINISHED |
| Object | Jews |
—
|
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: Jews | Statement: [1568 Edict of Torda, didNotExtendTo, Jews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotExtendTo Context triple: [1568 Edict of Torda, didNotExtendTo, Jews]
-
A.
doesNotCover
chosen
Indicates that one entity fails to include, protect, or extend over another entity or area.
-
B.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
C.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
D.
wasExtendedTo
Indicates that something previously existing was lengthened, expanded, or prolonged to reach a new limit, scope, or duration.
-
E.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37e34b88190bb4468424e2edf2d |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.