Triple
T32871511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Crown in right of Solomon Islands |
E840804
|
entity |
| Predicate | canBeReferredToAs |
P196912
|
FINISHED |
| Object | His Majesty in right of Solomon Islands |
—
|
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: His Majesty in right of Solomon Islands | Statement: [the Crown in right of Solomon Islands, canBeReferredToAs, His Majesty in right of Solomon Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeReferredToAs Context triple: [the Crown in right of Solomon Islands, canBeReferredToAs, His Majesty in right of Solomon Islands]
-
A.
canonicallyReferredToAs
Indicates that one entity is the officially recognized or standard name or label by which another entity is known.
-
B.
canBeNamed
Indicates that an entity is capable of being assigned or given a specific name or label.
-
C.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
D.
nameMayReferTo
Indicates that a given name or label can ambiguously denote or be used for one or more possible entities.
-
E.
isReferencedInNickname
Indicates that one entity is mentioned or alluded to within another entity’s nickname.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
| PDg | Predicate description generation | batch_69fe6e4801108190a6be6bec2d52a1b9 |
completed | May 8, 2026, 11:14 p.m. |
Created at: May 1, 2026, 1:17 a.m.