Triple
T4768587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosaic covenant |
E105870
|
entity |
| Predicate | basisOfRelationship |
P58659
|
FINISHED |
| Object | obedience to God’s law |
—
|
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: obedience to God’s law | Statement: [Mosaic covenant, basisOfRelationship, obedience to God’s law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisOfRelationship Context triple: [Mosaic covenant, basisOfRelationship, obedience to God’s law]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
relationshipDynamic
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
-
C.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
D.
relationshipFocus
Indicates a relationship where particular attention, priority, or emphasis is placed on the connection between two or more entities.
-
E.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6537eb80819096e0ae906c59d605 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:21 p.m.