Triple
T25082200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooke dynasty |
E628214
|
entity |
| Predicate | parentCountryAtEnd |
P160843
|
FINISHED |
| Object | United Kingdom |
—
|
NE NERFINISHED |
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: United Kingdom | Statement: [Brooke dynasty, parentCountryAtEnd, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCountryAtEnd Context triple: [Brooke dynasty, parentCountryAtEnd, United Kingdom]
-
A.
projectCountryAtTheTime
Indicates the country with which a project was associated at the specific time or period in question.
-
B.
parentCountryCode
Indicates that the value is the standardized country code of the country that has jurisdiction or primary association over the referenced entity.
-
C.
parentCountryOfOrigin
Indicates that one country is the original source or homeland from which another country historically emerged or originated.
-
D.
previousCountry
Indicates that one country was the immediately preceding country associated with, visited by, or occupied by a given entity before its current country.
-
E.
nativeCountry
Indicates the country in which an entity (typically a person) was born or is originally from.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f60ac643108190ae81561267155791 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f606c15af88190958856a9e467b826 |
completed | May 2, 2026, 2:14 p.m. |
Created at: April 18, 2026, 6:22 a.m.