Triple
T4609075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forfar County |
E100509
|
entity |
| Predicate | usedAsRegistrationCountyUntil |
P52130
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Forfar County, usedAsRegistrationCountyUntil, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsRegistrationCountyUntil Context triple: [Forfar County, usedAsRegistrationCountyUntil, 1975]
-
A.
usedAsCountyNameUntil
Indicates that an entity served as the official name of a county up to a specified point in time.
-
B.
hasHistoricRegistrationCountyStatus
Indicates that an entity holds or has held official historic registration status within a particular county.
-
C.
existedAsCountyUntil
chosen
Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
-
D.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
E.
associatedWithCounty
Indicates that an entity has a relationship or linkage to a specific county, such as jurisdiction, location, or administrative association.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd599f08d88190ad4bed8bafb592cd |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.