Triple
T31064460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bar Kokhba forces |
E791628
|
entity |
| Predicate | insigniaFeatured |
P105303
|
FINISHED |
| Object | Jewish symbols |
—
|
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: Jewish symbols | Statement: [Bar Kokhba forces, insigniaFeatured, Jewish symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaFeatured Context triple: [Bar Kokhba forces, insigniaFeatured, Jewish symbols]
-
A.
insigniaCaption
Indicates the text that serves as a caption or explanatory label specifically for an insignia.
-
B.
insigniaDesignFeature
chosen
Indicates a design element or characteristic that forms part of an insignia.
-
C.
insigniaName
Indicates the specific name or designation assigned to an insignia associated with an entity.
-
D.
insigniaContext
Indicates the contextual relationship in which an insignia is used, displayed, or holds meaning (such as organizational, temporal, or situational context).
-
E.
insigniaUsedFor
Indicates that a particular insignia is employed or designated for a specific purpose, function, or use.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69579eda48190b1bd6e7ce026b538 |
completed | May 3, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:01 p.m.