Triple
T19082660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binah |
E467067
|
entity |
| Predicate | functionInPsyche |
P134295
|
FINISHED |
| Object | capacity to understand and differentiate |
—
|
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: capacity to understand and differentiate | Statement: [Binah, functionInPsyche, capacity to understand and differentiate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInPsyche Context triple: [Binah, functionInPsyche, capacity to understand and differentiate]
-
A.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
-
B.
functionInBeliefSystem
Indicates that one entity serves a particular role, purpose, or function within the structure or doctrine of a belief system.
-
C.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
D.
functionInPractice
Indicates that an entity serves a particular role or performs a specific function in actual use or real-world practice.
-
E.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2eab58c8190a987c88d633c92ec |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.