Triple
T8525439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkansas Territory |
E201802
|
entity |
| Predicate | admittedEntityDate |
P205
|
FINISHED |
| Object | 1836-06-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: 1836-06-15 | Statement: [Arkansas Territory, admittedEntityDate, 1836-06-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admittedEntityDate Context triple: [Arkansas Territory, admittedEntityDate, 1836-06-15]
-
A.
admissionDate
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.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
C.
accessionDate
Indicates the date on which an item, record, or entity was formally added to a collection, system, or repository.
-
D.
admittedToUnionOn
chosen
Indicates that an entity (typically a state or region) was formally accepted and incorporated into a union or federation on a specific date.
-
E.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe644c4648190a14dcaeaa90d72c7 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.