Triple
T17818499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross and Cromarty |
E444909
|
entity |
| Predicate | unifiedAsCountyInYear |
P129020
|
FINISHED |
| Object | 1889 |
—
|
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: 1889 | Statement: [Ross and Cromarty, unifiedAsCountyInYear, 1889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unifiedAsCountyInYear Context triple: [Ross and Cromarty, unifiedAsCountyInYear, 1889]
-
A.
existedAsCountyUntil
Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
-
B.
hasConsolidatedCityCountySince
Indicates that a city and county have been formally consolidated into a single unified government entity starting from a specified point in time.
-
C.
hasFormerCounty
Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
-
D.
enteredUnionAsCounty
Indicates that an entity became part of a political union specifically with the status or designation of a county.
-
E.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e488812df081909771d51c54c405fe |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:14 a.m.