Triple
T36055807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Procureur General of Guernsey |
E1042943
|
entity |
| Predicate | sharesCollectiveTitleWith |
P29696
|
FINISHED |
| Object | HM Comptroller (Guernsey) |
—
|
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: HM Comptroller (Guernsey) | Statement: [Procureur General of Guernsey, sharesCollectiveTitleWith, HM Comptroller (Guernsey)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCollectiveTitleWith Context triple: [Procureur General of Guernsey, sharesCollectiveTitleWith, HM Comptroller (Guernsey)]
-
A.
sharesCollectivityWith
Indicates that two or more entities participate together as members of the same collective, group, or shared whole.
-
B.
sharesTitleWith
chosen
Indicates that two entities have the same title or name.
-
C.
sharesCollectionWith
Indicates that one entity has a collection that is shared with another entity, granting them mutual access or association with the same set of items.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: May 3, 2026, 4:08 p.m.