Triple
T373042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Articles of Confederation |
E8310
|
entity |
| Predicate | approvedByCongressOn |
P1036
|
FINISHED |
| Object | 1777-11-15 |
—
|
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: 1777-11-15 | Statement: [Articles of Confederation, approvedByCongressOn, 1777-11-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedByCongressOn Context triple: [Articles of Confederation, approvedByCongressOn, 1777-11-15]
-
A.
ratifiedOn
chosen
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
-
B.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
-
C.
stateOfFirstRatification
Indicates the state in which an agreement, treaty, or document was first formally ratified.
-
D.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
-
E.
ratificationMethod
Indicates the process or formal procedure by which an agreement, decision, or document is officially approved and made valid.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec018d508190b5687a9ba90b3092 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.