Triple
T4879538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Micah (Book of Judges) |
E109289
|
entity |
| Predicate | textualMottoContext |
P59577
|
FINISHED |
| Object | "In those days there was no king in Israel" |
—
|
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: "In those days there was no king in Israel" | Statement: [Micah (Book of Judges), textualMottoContext, "In those days there was no king in Israel"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualMottoContext Context triple: [Micah (Book of Judges), textualMottoContext, "In those days there was no king in Israel"]
-
A.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
B.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
C.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
D.
mottoInterpretation
Indicates the explanatory relationship between a motto and its intended meaning or message.
-
E.
mottoInscription
Indicates that a particular motto is inscribed on or associated as an inscription with an entity.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbf37ac819085bb758bc6406271 |
completed | March 20, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6d5976a081909090c0c263f6e9b7 |
completed | March 20, 2026, 3:52 p.m. |
Created at: March 20, 2026, 1:27 p.m.