Triple
T23575385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Society of Mary |
E580239
|
entity |
| Predicate | hasConstitutionApprovedInYear |
P153231
|
FINISHED |
| Object | 1839 |
—
|
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: 1839 | Statement: [Society of Mary, hasConstitutionApprovedInYear, 1839]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstitutionApprovedInYear Context triple: [Society of Mary, hasConstitutionApprovedInYear, 1839]
-
A.
congressionalApprovalYear
Indicates the year in which a given item, action, or measure received formal approval by a legislative congress.
-
B.
lastConstitutionAdopted
Indicates that a particular constitution was the most recently adopted constitution of a given political entity or jurisdiction.
-
C.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
-
D.
amendmentYear
Indicates the year in which an amendment to a law, document, or agreement was formally made or enacted.
-
E.
majorAmendmentYear
Indicates the year in which a significant or major amendment was made to something (such as a document, law, or agreement).
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd5a7e88190ba348d58e552bd3c |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:38 p.m.