Triple
T37781836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Árva |
E941850
|
entity |
| Predicate | timePeriodAsCounty |
P194504
|
FINISHED |
| Object | from Middle Ages until 1918 |
—
|
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: from Middle Ages until 1918 | Statement: [Árva, timePeriodAsCounty, from Middle Ages until 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodAsCounty Context triple: [Árva, timePeriodAsCounty, from Middle Ages until 1918]
-
A.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
B.
unifiedAsCountyInYear
Indicates that multiple areas or jurisdictions were merged into a single county in the specified year.
-
C.
timePeriodAsAdministrativeCenter
Indicates the span of time during which a place functioned as an administrative center for a governing body or jurisdiction.
-
D.
establishedAsCountyInCurrentForm
Indicates that an administrative region became a county in its present organizational or territorial form on a specific date or during a specific period.
-
E.
startCounty
Indicates the county in which something (such as an event, route, or process) begins or originates.
- F. None of above. chosen
Provenance (4 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: May 3, 2026, 4:19 p.m.