Triple
T31172966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgar |
E794662
|
entity |
| Predicate | contrastsWithGroup |
P112793
|
FINISHED |
| Object | Puritans |
—
|
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: Puritans | Statement: [Edgar, contrastsWithGroup, Puritans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contrastsWithGroup Context triple: [Edgar, contrastsWithGroup, Puritans]
-
A.
initiallyContrastsWith
Indicates that one entity is first presented or perceived in opposition or contrast to another entity at the beginning of a sequence, process, or context.
-
B.
providesContrastWith
Indicates that one entity is used to highlight differences or distinctions when compared with another entity.
-
C.
contrastsPredicate
chosen
Indicates that one entity is presented in opposition or difference to another, highlighting their contrasting characteristics or qualities.
-
D.
contrastsForm
Indicates that one form is presented in opposition or comparison to another form to highlight their differences.
-
E.
contrastedWithObject
Indicates that one entity is explicitly compared to another by highlighting their differences or opposing characteristics.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 29, 2026, 9:07 p.m.