Triple
T37628924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheba (biblical region) |
E936286
|
entity |
| Predicate | diplomaticContactWith |
P15536
|
FINISHED |
| Object | King Solomon |
—
|
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: King Solomon | Statement: [Sheba (biblical region), diplomaticContactWith, King Solomon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticContactWith Context triple: [Sheba (biblical region), diplomaticContactWith, King Solomon]
-
A.
diplomaticConnections
Indicates the existence of formal or informal diplomatic relationships or channels of communication between two entities.
-
B.
diplomaticRelation
chosen
Indicates a formal relationship of negotiation, communication, or representation between political entities, typically states or governments.
-
C.
diplomaticAssociation
Indicates a formal diplomatic relationship or affiliation that exists or is established between two or more entities.
-
D.
hasDiplomaticStaffFrom
Indicates that an entity has diplomatic personnel who originate from or represent another specified entity.
-
E.
diplomaticRelationContext
Indicates the contextual circumstances, conditions, or framework within which a diplomatic relationship between entities exists or is conducted.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.