Triple
T3176535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Arch Masonry |
E66477
|
entity |
| Predicate | hasOfficerTitle |
P974
|
FINISHED |
| Object | King |
E280718
|
NE 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: King | Statement: [Royal Arch Masonry, hasOfficerTitle, King]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: King Context triple: [Royal Arch Masonry, hasOfficerTitle, King]
-
A.
King
The King is the reigning male monarch who serves as the head of state of the United Kingdom within its constitutional monarchy system.
-
B.
King
King is a township in the Regional Municipality of York in Ontario, Canada, known for its rural landscapes, rolling hills, and equestrian farms within the Greater Toronto Area.
-
C.
King
The King of Norway is the constitutional monarch and ceremonial head of state in Norway’s parliamentary system.
-
D.
King
King is a prominent video game company best known for creating the massively popular mobile puzzle game Candy Crush Saga.
-
E.
King
chosen
King is a regal title traditionally denoting a male sovereign ruler of a kingdom, often associated with supreme authority and hereditary monarchy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69b0bec8190957913b44d876079 |
completed | March 8, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b235f16e60819091cbdb76130ecc40 |
completed | March 12, 2026, 3:41 a.m. |
Created at: March 8, 2026, 3:06 p.m.