Triple
T21410982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware |
E528165
|
entity |
| Predicate | ratificationOrderOfUSConstitution |
P19310
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Delaware, ratificationOrderOfUSConstitution, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratificationOrderOfUSConstitution Context triple: [Delaware, ratificationOrderOfUSConstitution, 1]
-
A.
ratificationOrder
chosen
Indicates the sequence or priority in which ratifications of an agreement, treaty, or decision are made or recognized.
-
B.
ratificationMethod
Indicates the process or formal procedure by which an agreement, decision, or document is officially approved and made valid.
-
C.
numberOfStatesRequiredForRatification
Indicates the specific number of states that must approve or ratify a proposal for it to become valid or effective.
-
D.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
-
E.
stateOfFirstRatification
Indicates the state in which an agreement, treaty, or document was first formally ratified.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1b6595481908cdf915e3585ed08 |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:43 p.m.