Triple
T28320633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Precious Organisation |
E717267
|
entity |
| Predicate | notableCountryOfRelease |
P202829
|
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: [The Precious Organisation, notableCountryOfRelease, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCountryOfRelease Context triple: [The Precious Organisation, notableCountryOfRelease, United Kingdom]
-
A.
notableCountry
Indicates that a country holds particular significance or prominence in relation to the subject entity.
-
B.
notableHolderCountry
Indicates that a country is recognized as a significant or notable holder of a particular item, title, record, or distinction.
-
C.
notableProjectCountry
Indicates that a country is associated with a notable project undertaken by the subject.
-
D.
notableNationality
Indicates that an entity is notably associated with a particular nationality, often by origin, citizenship, or cultural identity.
-
E.
notableCountrySection
Indicates that a specific section or part of a country is particularly notable or significant in some context.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a00c3362dcc819096e49b882709fddd |
completed | May 10, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_6a00c2e5cdd88190a5f2d0f6a843cd56 |
completed | May 10, 2026, 5:39 p.m. |
| PDg | Predicate description generation | batch_6a00c3355498819088253d5e5c17267f |
completed | May 10, 2026, 5:41 p.m. |
Created at: April 28, 2026, 12:24 a.m.