Triple
T23352379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thummim |
E592949
|
entity |
| Predicate | consultationContext |
P125712
|
FINISHED |
| Object | national decisions |
—
|
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: national decisions | Statement: [Thummim, consultationContext, national decisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consultationContext Context triple: [Thummim, consultationContext, national decisions]
-
A.
consultationSetting
chosen
Indicates the context or environment in which a consultation or advisory interaction takes place.
-
B.
consultsOn
Indicates that one entity provides expert advice, guidance, or professional input to another entity regarding a specific subject, project, or decision.
-
C.
typicalAppointmentContext
Indicates the usual situational setting or circumstances in which an appointment typically occurs.
-
D.
clinicalContext
Indicates the medical situation, setting, or circumstances under which a clinical finding, observation, or action occurs.
-
E.
consulted
Indicates that one entity sought advice, information, or guidance from another entity.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a14e04c81909c007b97cf5378b6 |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:20 p.m.