Triple
T26397344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General (United Kingdom) |
E663601
|
entity |
| Predicate | typicalRankCodeUK |
P48323
|
FINISHED |
| Object | 4-star |
—
|
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: 4-star | Statement: [General (United Kingdom), typicalRankCodeUK, 4-star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRankCodeUK Context triple: [General (United Kingdom), typicalRankCodeUK, 4-star]
-
A.
classificationByUK
Indicates a relationship where an entity is assigned a category, status, or type according to a United Kingdom–specific classification system.
-
B.
comparativeRankUK
Indicates that one entity’s rank or position is being compared to another’s specifically within a United Kingdom–based ranking system.
-
C.
depthRankInBritishIsles
Indicates the relative ordering of an entity by depth compared to other entities within the British Isles.
-
D.
hasPopulationRankInUK
Indicates the relative position of an entity’s population size compared to other entities within the United Kingdom.
-
E.
rankCode
chosen
Indicates the specific rank or hierarchical level assigned to an entity, typically encoded as a standardized 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: April 26, 2026, 11:29 p.m.