Triple
T6458673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gentile Christians |
E142059
|
entity |
| Predicate | didNotFullyAdopt |
P58067
|
FINISHED |
| Object | Jewish 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: Jewish law | Statement: [Gentile Christians, didNotFullyAdopt, Jewish law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotFullyAdopt Context triple: [Gentile Christians, didNotFullyAdopt, Jewish law]
-
A.
notFullyAdoptedIn
chosen
Indicates that something has not been completely or universally implemented, accepted, or put into practice within a specified context or domain.
-
B.
didNotBecome
Indicates that an expected or potential change of state, role, or condition between entities did not occur.
-
C.
notFullyIncorporated
Indicates that one entity has not been completely integrated, absorbed, or merged into another entity or system.
-
D.
hadLimitedAdoptionIn
Indicates that something was adopted or taken up to only a small or restricted extent within a particular context, group, or region.
-
E.
doesNotFullyExplain
Indicates that one entity’s explanation of another entity, event, or situation is incomplete or insufficient to account for it fully.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069f347f48190a2b22c5b648b17bd |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.