Triple
T23819982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Székely Land |
E589204
|
entity |
| Predicate | historicalAdministrativeReform |
P117243
|
FINISHED |
| Object | 1876 |
—
|
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: 1876 | Statement: [Székely Land, historicalAdministrativeReform, 1876]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalAdministrativeReform Context triple: [Székely Land, historicalAdministrativeReform, 1876]
-
A.
partOfAdministrativeDivisionReform
chosen
Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
-
B.
municipalityReform
Indicates a formal reorganization or restructuring of a municipality’s administrative boundaries, governance, or status.
-
C.
administrativeHistory
Indicates the sequence of past administrative changes, statuses, or governing arrangements that have affected an entity over time.
-
D.
historicAdministrativeUnit
Indicates that an entity functioned as an official administrative unit or division during a past or no-longer-current historical period.
-
E.
regionBeforeReform
Indicates that a region is defined or considered as it existed prior to a specific reform or reorganization.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7ae4f8c8190a92621861cbae2f4 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.