Triple
T13825278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiram Abiff |
E332233
|
entity |
| Predicate | employer |
P7
|
FINISHED |
| Object | King Solomon |
E4651
|
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 Solomon | Statement: [Hiram Abiff, employer, King Solomon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: King Solomon Context triple: [Hiram Abiff, employer, King Solomon]
-
A.
King Solomon
chosen
King Solomon is a biblical king of ancient Israel renowned for his wisdom, wealth, and the construction of the First Temple in Jerusalem.
-
B.
Solomon
Solomon is an Australian federal electoral division in the Northern Territory that includes the Darwin urban area and surrounding regions.
-
C.
Solomon
Solomon is the given first name of the American conceptual artist and minimalist pioneer Sol LeWitt.
-
D.
Solomon
Solomon is a common Hebrew-origin surname borne by numerous individuals across diverse cultures and professions.
-
E.
Solomon
Solomon is a small city in Kansas, United States, known for its rural character and location spanning Dickinson and Saline counties.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0285fb7c8190be4b90bdc0d6fa53 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8e85c6c81908bdf5d43b917d151 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:13 p.m.