Triple
T26622624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin Coffin III |
E668242
|
entity |
| Predicate | offersDealTo |
P177105
|
FINISHED |
| Object | Mark Cohen |
—
|
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: Mark Cohen | Statement: [Benjamin Coffin III, offersDealTo, Mark Cohen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersDealTo Context triple: [Benjamin Coffin III, offersDealTo, Mark Cohen]
-
A.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
B.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
-
C.
offersObject
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
D.
offersAccess
Indicates that one entity provides another entity with the ability or permission to use, enter, or interact with a resource, service, or location.
-
E.
offersInterface
Indicates that one entity provides or exposes a specific interface that another entity can use or interact with.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 27, 2026, 2:21 a.m.