Triple
T4091767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kibbutz movement |
E87718
|
entity |
| Predicate | transitionTrend |
P39078
|
FINISHED |
| Object | privatization of services |
—
|
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: privatization of services | Statement: [Kibbutz movement, transitionTrend, privatization of services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionTrend Context triple: [Kibbutz movement, transitionTrend, privatization of services]
-
A.
transition
Indicates a change of state or condition from one form, phase, or situation to another.
-
B.
trends
chosen
Indicates that one entity exhibits a general direction of change or development over time in relation to another reference or context.
-
C.
transitionProgram
Indicates a relationship where one entity serves as a program or structured process that facilitates another entity’s transition from one state, phase, or condition to another.
-
D.
transitionTo
Indicates a change in state, condition, or phase from one defined status to another.
-
E.
hasTrend
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcae22a081908af65a960306b78c |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.