Triple
T35785627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Israel |
E1034555
|
entity |
| Predicate | locationOfMenorah |
P176574
|
FINISHED |
| Object | center of shield |
—
|
LITERAL 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: center of shield | Statement: [coat of arms of Israel, locationOfMenorah, center of shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfMenorah Context triple: [coat of arms of Israel, locationOfMenorah, center of shield]
-
A.
positionInMenorah
Indicates the specific location or ordering of an element within a menorah structure.
-
B.
menorahType
Indicates the specific kind or category of menorah associated with an entity.
-
C.
ornamentLocation
chosen
Indicates the spatial or positional relationship specifying where an ornament is placed or located relative to another object or context.
-
D.
locationOfAleph
Indicates the specific place or position where the entity referred to as Aleph is situated or found.
-
E.
positionOnJerusalem
Indicates that one entity occupies or is located at a specific position within the area of Jerusalem.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.