Triple
T31693873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Penn |
E808867
|
entity |
| Predicate | signedDocumentOnBehalfOf |
P6229
|
FINISHED |
| Object | North Carolina |
—
|
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: North Carolina | Statement: [John Penn, signedDocumentOnBehalfOf, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedDocumentOnBehalfOf Context triple: [John Penn, signedDocumentOnBehalfOf, North Carolina]
-
A.
documentSignedBy
Indicates that a document has been formally signed or authorized by a specific entity.
-
B.
signedByRepresentativeOf
chosen
Indicates that an item (such as a document or agreement) has been signed on behalf of a party by that party’s authorized representative.
-
C.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
D.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
E.
signatureRoleOf
Indicates that an entity serves in a specific role or capacity within the context of a particular signature.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:09 p.m.