Triple
T18882805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Ratifying Convention |
E461873
|
entity |
| Predicate | ratifyingStateNumber |
P19310
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [New York Ratifying Convention, ratifyingStateNumber, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratifyingStateNumber Context triple: [New York Ratifying Convention, ratifyingStateNumber, 11]
-
A.
ratificationOrder
chosen
Indicates the sequence or priority in which ratifications of an agreement, treaty, or decision are made or recognized.
-
B.
numberOfStatesRequiredForRatification
Indicates the specific number of states that must approve or ratify a proposal for it to become valid or effective.
-
C.
numberOfStatesRepresented
Indicates how many distinct states are represented or covered in a given context or entity.
-
D.
stateOfFirstRatification
Indicates the state in which an agreement, treaty, or document was first formally ratified.
-
E.
representedState
Indicates that one entity serves as a representation or depiction of the state or condition of another entity.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d3286081908c1ae2cb413b49aa |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:57 a.m.