Triple
T158745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mezuzah |
E3233
|
entity |
| Predicate | isCommandedIn |
P6842
|
FINISHED |
| Object | Deuteronomy 6:9 |
—
|
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: Deuteronomy 6:9 | Statement: [mezuzah, isCommandedIn, Deuteronomy 6:9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommandedIn Context triple: [mezuzah, isCommandedIn, Deuteronomy 6:9]
-
A.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
B.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
C.
notCommanderOf
Indicates that a given entity does not hold a commanding or leadership role over another specified entity.
-
D.
isCommanderInChiefOf
Indicates that one entity holds the highest authority and ultimate command over the armed forces or military organization of another entity.
-
E.
successorInCommand
Indicates that one entity is designated to assume command authority immediately after another entity, typically when the latter is unavailable or their term ends.
- F. None of above. chosen
Provenance (4 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.