Triple
T26622627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin Coffin III |
E668242
|
entity |
| Predicate | offerCondition |
P80568
|
FINISHED |
| Object | stop Maureen’s protest |
—
|
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: stop Maureen’s protest | Statement: [Benjamin Coffin III, offerCondition, stop Maureen’s protest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offerCondition Context triple: [Benjamin Coffin III, offerCondition, stop Maureen’s protest]
-
A.
conditionOfOffer
chosen
Indicates the terms, requirements, or circumstances under which an offer is valid or applies.
-
B.
promotionConditions
Indicates the conditions or criteria that must be met for a promotion to occur between entities.
-
C.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
-
D.
conditionOfBargain
Indicates that one entity is a term, stipulation, or requirement that forms part of the agreed exchange in a bargain or contract.
-
E.
offersAccess
Indicates that one entity provides another entity with the ability or permission to use, enter, or interact with a resource, service, or location.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 2:21 a.m.