Triple
T9504329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulekites |
E229223
|
entity |
| Predicate | lostKnowledgeOf |
P22661
|
FINISHED |
| Object | full law of Moses |
—
|
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: full law of Moses | Statement: [Mulekites, lostKnowledgeOf, full law of Moses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostKnowledgeOf Context triple: [Mulekites, lostKnowledgeOf, full law of Moses]
-
A.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
B.
ignorantOf
chosen
Indicates that one entity lacks knowledge or awareness of another entity or of some specific fact, topic, or situation.
-
C.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
D.
knowledgeOutput
Indicates that an entity produces, expresses, or makes available knowledge, information, or learned content as an output.
-
E.
knowledgeType
Indicates the specific category or nature of knowledge associated with an entity or statement (e.g., factual, procedural, conceptual).
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9840148081908df237f212b62e67 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.