Triple
T34223249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Counties of the Republic of Ireland |
E877980
|
entity |
| Predicate | numberOfTraditionalCounties |
P27148
|
FINISHED |
| Object | 26 |
—
|
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: 26 | Statement: [Counties of the Republic of Ireland, numberOfTraditionalCounties, 26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfTraditionalCounties Context triple: [Counties of the Republic of Ireland, numberOfTraditionalCounties, 26]
-
A.
hasNumberOfCounties
chosen
Indicates the relationship that specifies how many counties are associated with or contained within a given entity.
-
B.
numberPerCounty
Indicates the quantity or count of something associated with each individual county.
-
C.
hasTraditionalCountyStatus
Indicates that an entity holds the official or customary status of being recognized as a traditional county within a given jurisdiction.
-
D.
hasNumberOfTownships
Indicates the specific count of townships associated with or contained within a given entity.
-
E.
hasNumberOfTraditionalChiefdoms
Indicates the relationship that specifies how many traditional chiefdoms are associated with a given entity.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.