Triple
T36182426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binx |
E1046751
|
entity |
| Predicate | yearOfCurse |
P196440
|
FINISHED |
| Object | 1693 |
—
|
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: 1693 | Statement: [Binx, yearOfCurse, 1693]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfCurse Context triple: [Binx, yearOfCurse, 1693]
-
A.
timeOfCurse
Indicates the specific time at which a curse is cast, activated, or takes effect in relation to an entity or event.
-
B.
placeOfCurse
Indicates the specific location where a curse is cast, placed, or takes effect on an entity.
-
C.
yearOfSevenGrievances
Indicates the specific year in which the event or period referred to as the "Seven Grievances" occurred or was established.
-
D.
associatedCurse
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
E.
curseName
Indicates that one entity assigns, uses, or is associated with a specific name or label used as a curse toward 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
| PDg | Predicate description generation | batch_69fe349739cc8190a21c408208312e6c |
completed | May 8, 2026, 7:08 p.m. |
Created at: May 3, 2026, 4:08 p.m.