Triple
T26873333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seneca Falls Convention |
E676675
|
entity |
| Predicate | includedRightDemanded |
P96022
|
FINISHED |
| Object | women's right to vote |
—
|
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: women's right to vote | Statement: [Seneca Falls Convention, includedRightDemanded, women's right to vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedRightDemanded Context triple: [Seneca Falls Convention, includedRightDemanded, women's right to vote]
-
A.
includesRight
chosen
Indicates that one entity contains, encompasses, or grants a particular right to another entity.
-
B.
includedSingle
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
-
C.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
incorporatesRight
Indicates that one entity includes, absorbs, or integrates another entity as a component or part within itself.
-
E.
supportedRight
Indicates that one entity endorsed, upheld, or actively backed the right or entitlement held by another entity.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 27, 2026, 5:34 a.m.