Triple
T18142771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulster Covenant |
E434302
|
entity |
| Predicate | methodOfSigning |
P105541
|
FINISHED |
| Object | public mass signing |
—
|
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: public mass signing | Statement: [Ulster Covenant, methodOfSigning, public mass signing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfSigning Context triple: [Ulster Covenant, methodOfSigning, public mass signing]
-
A.
signingProcedure
chosen
Indicates the formal process or method by which an agreement, document, or contract is signed or executed between parties.
-
B.
signingConvention
Indicates that one party formally agrees to and adopts the terms of a convention, treaty, or formal agreement.
-
C.
mayBeSignedAs
Indicates that one entity can optionally be used or recognized as the signature or signed form of another entity.
-
D.
signingStandard
Indicates that an entity conforms to, uses, or is governed by a particular standard or specification for signing (e.g., digital signatures or formal approvals).
-
E.
signatureType
Indicates the specific kind or category of a signature associated with an entity or action.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0c8aa88190b4ded7e6d05f6edf |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.