Triple
T36173388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelical Lutheran Church in Canada |
E1046507
|
entity |
| Predicate | dateSignedWaterlooDeclaration |
P184998
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Evangelical Lutheran Church in Canada, dateSignedWaterlooDeclaration, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateSignedWaterlooDeclaration Context triple: [Evangelical Lutheran Church in Canada, dateSignedWaterlooDeclaration, 2001]
-
A.
signedDeclarationOfIndependence
Indicates that the subject formally endorsed and signed a specific Declaration of Independence document.
-
B.
foundingTreatySignedAt
Indicates that the founding treaty establishing an entity was formally signed at a specific location.
-
C.
SanquharDeclarationContent
Indicates that the content expresses or pertains to the declarations made in the Sanquhar Declaration.
-
D.
placeOfProclamation
Indicates the location where an official announcement, declaration, or proclamation is formally made.
-
E.
dateOfConstitutionSigning
Indicates the date on which a constitution was formally signed or adopted.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.