Triple
T19036514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Ulster |
E465885
|
entity |
| Predicate | hasTraditionalCountyCount |
P27148
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Province of Ulster, hasTraditionalCountyCount, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalCountyCount Context triple: [Province of Ulster, hasTraditionalCountyCount, 9]
-
A.
hasTraditionalCountyStatus
Indicates that an entity holds the official or customary status of being recognized as a traditional county within a given jurisdiction.
-
B.
hasNumberOfCounties
chosen
Indicates the relationship that specifies how many counties are associated with or contained within a given entity.
-
C.
hasHistoricCountyNumber
Indicates that an entity is associated with a specific identifier corresponding to its historic county designation.
-
D.
traditionalCountyIncludes
Indicates that a traditional or historic county geographically contains or encompasses another area or entity within its boundaries.
-
E.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d744b39881909334a80a4c15000b |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.