Triple
T10127966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leuenberg Agreement |
E226261
|
entity |
| Predicate | hasSignatoryType |
P447
|
FINISHED |
| Object | Lutheran churches |
—
|
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: Lutheran churches | Statement: [Leuenberg Agreement, hasSignatoryType, Lutheran churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatoryType Context triple: [Leuenberg Agreement, hasSignatoryType, Lutheran churches]
-
A.
signatoryType
chosen
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
B.
hasSignTypes
Indicates that an entity is associated with one or more specific types or categories of signs.
-
C.
hasSignatories
Indicates that one or more parties have formally signed or endorsed an agreement, document, or instrument.
-
D.
hasSignatureStatusFor
Indicates that a specific entity holds or is assigned a particular signature-related status in relation to another entity or context.
-
E.
hasSignatureRole
Indicates that an entity holds a primary, defining, or officially recognized role within a given context or relationship.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2f0a0e881909267a83fbeb31f0c |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.