Triple
T13240088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | entrance of Solomon’s Temple |
E315257
|
entity |
| Predicate | flankedBy |
P20134
|
FINISHED |
| Object | Jachin |
E80151
|
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: Jachin | Statement: [entrance of Solomon’s Temple, flankedBy, Jachin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jachin Context triple: [entrance of Solomon’s Temple, flankedBy, Jachin]
-
A.
Jachin
chosen
Jachin is one of the two bronze pillars that stood at the entrance of Solomon’s Temple in Jerusalem, symbolizing stability and divine establishment.
-
B.
Jashub
Jashub is a biblical figure mentioned in the Hebrew Bible as one of the descendants of Jacob through the tribe of Issachar.
-
C.
Yakhin
Yakhin is a variant form of the biblical name Jachin, traditionally associated with one of the two pillars of Solomon’s Temple.
-
D.
Jachim
Jachim is a given name that serves as a variant form of Joachim, used in various European naming traditions.
-
E.
Jamtha
Jamtha is a locality on the outskirts of Nagpur in Maharashtra, India, known primarily for hosting the Vidarbha Cricket Association Stadium.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5850ac8190849a51da39efe5be |
completed | April 10, 2026, 11:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff323a3c8190b46b24e69e653105 |
completed | May 3, 2026, 7:54 a.m. |
Created at: April 9, 2026, 9:23 p.m.