Triple
T35504235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyandotte Constitution |
E1026096
|
entity |
| Predicate | admissionDateRelated |
P25175
|
FINISHED |
| Object | 1861-01-29 |
—
|
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: 1861-01-29 | Statement: [Wyandotte Constitution, admissionDateRelated, 1861-01-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionDateRelated Context triple: [Wyandotte Constitution, admissionDateRelated, 1861-01-29]
-
A.
admissionDate
chosen
Indicates the date on which an entity (such as a person, application, or item) is formally admitted, accepted, or entered into a system or institution.
-
B.
admissionActDate
Indicates the date on which an admission-related action or event formally took place.
-
C.
AUAdmissionDate
Indicates the date on which an entity is formally admitted or accepted into AU (e.g., an institution, program, or system).
-
D.
admittedTo
Indicates that one entity has been formally accepted, enrolled, or granted entry into another entity, such as an institution, program, or facility.
-
E.
UNAdmissionDate
Indicates the date on which an entity was officially admitted as a member of the United Nations.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.